beats-like-a-helix04/11/2022, 8:57 PM
gives me this complaint while being used within Kedro:
Does anyone have an idea how I can fix this? Cheers.
from pycbc.waveform import get_fd_waveform File "/Users/jordan/mambaforge/envs/gravitational_waves/lib/python3.8/site-packages/pycbc/__init__.py", line 150, in <module> multiprocessing.set_start_method('fork') File "/Users/jordan/mambaforge/envs/gravitational_waves/lib/python3.8/multiprocessing/context.py", line 243, in set_start_method raise RuntimeError('context has already been set') RuntimeError: context has already been set
datajoely04/12/2022, 4:02 PM
beats-like-a-helix04/12/2022, 4:16 PM
avan-sh04/13/2022, 9:52 AM
. Due to this, any possible of multiprocessing context that might be set before importing pycbc is likely to create similar error. Possibly pycbc kill/remove any context before trying to create a new one as it is always possible that other imports that precede could set a context already. (Not sure if this removing context is correct or even correct) In this case kedro is not using any multiprocessing functions, but has an import of multiprocessing which is somehow creating a context. A quick fix to unblock your development is to importing pycbc in your bin/kedro before any kedro import. Another option that works is to comment out the ShelveStore code in your
module in your local installation. Sadly, both are temporary fixes, I don't have anything permanent
beats-like-a-helix04/13/2022, 5:48 PM
or the same error will occur, but this is a small price to pay.
datajoely04/13/2022, 5:49 PM
beats-like-a-helix04/13/2022, 5:50 PM
avan-sh04/14/2022, 2:27 AM
datajoely04/14/2022, 4:16 AM
avan-sh04/14/2022, 5:40 PM