As it stands, CHIME/FRB specific packages are required (although hidden as imports in the backend/chimefrb.py data reader). To alleviate this and ensure that fitburst functionality is accessible while not having those specific packages installed, I've slightly modified the data reader class to only load the chime_frb_api and cfod packages as they are needed, and report an informative error when not found.
As an extension to this, we can list those two CHIME packages as optional extras in the setup.cfg file so that a user can still install them via a pip, although with an additional tag, e.g.,
cd fitburst
pip install .[chimefrb]
(Obviously, if the user does not have the credentials required to access the CHIME/FRB package then this will fail, but that is not within the scope of fitburst.)
As it stands, CHIME/FRB specific packages are required (although hidden as imports in the
backend/chimefrb.py
data reader). To alleviate this and ensure thatfitburst
functionality is accessible while not having those specific packages installed, I've slightly modified the data reader class to only load thechime_frb_api
andcfod
packages as they are needed, and report an informative error when not found.As an extension to this, we can list those two CHIME packages as optional extras in the
setup.cfg
file so that a user can still install them via apip
, although with an additional tag, e.g.,(Obviously, if the user does not have the credentials required to access the CHIME/FRB package then this will fail, but that is not within the scope of
fitburst
.)