Closed jpdeleon closed 2 weeks ago
Hmm... there should already be a workaround implemented if SVO is not responding. Perhaps it only works on initialization and if SVO stops responding afterward, then it won't fall back to the webbpsf profiles. Can you show the error traceback?
The pipeline is working incredibly well. I just had trouble proceeding to the Level 3: PSF subtraction part because SVO database is currently down (which happens not infrequently). Does it make sense to have the JWST coronagraphy filter profiles included in the package to avoid this bottleneck?