You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A help desk ticket (INC0182968) has exposed a weakness in our documentation regarding the use of parallel processing in the pipeline.
If multiprocessing is active, when running from a script (i.e. python multiproc_detector1.py), importing that script must not spawn more processes. This is typically prevented by placing process-spawning code inside the if __name__ == '__main__': block.
Users are not warned of this requirement in the documentation; if not followed, this will lead to a system crash as the code will attempt to spawn an ever-increasing number of processes.
The text was updated successfully, but these errors were encountered:
stscijgbot-jp
changed the title
Multiprocessed ramp_fit data leads to parallel Detector1Pipeline processes?
Documentation improvement for multiprocessing: a script which spawns processes on import will cause system failure
Oct 20, 2022
Issue JP-2980 was created on JIRA by Tyler Pauly:
A help desk ticket (INC0182968) has exposed a weakness in our documentation regarding the use of parallel processing in the pipeline.
If multiprocessing is active, when running from a script (i.e.
python multiproc_detector1.py
), importing that script must not spawn more processes. This is typically prevented by placing process-spawning code inside theif __name__ == '__main__':
block.Users are not warned of this requirement in the documentation; if not followed, this will lead to a system crash as the code will attempt to spawn an ever-increasing number of processes.
The text was updated successfully, but these errors were encountered: