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
Right now some preprocessing parameters are loaded from the instrument, and then overriden by kwargs to the run() function.
I think it is very unlikely that we will run multiple instruments' images using the same config file, so it would be simpler to just put all the parameters (e.g., which preprocessing steps need to be done) into the config, load them as critical parameters, and then have that be the only point of configuration for the preprocessing.
The text was updated successfully, but these errors were encountered:
The way it works right now makes it impossible to figure out the provenances before actually running the preprocessing. This needs to fixed. I am putting in a hack that assumes we are using all the preprocessing steps but it needs to go into the parameters of the preprocessor object.
Right now some preprocessing parameters are loaded from the instrument, and then overriden by kwargs to the run() function.
I think it is very unlikely that we will run multiple instruments' images using the same config file, so it would be simpler to just put all the parameters (e.g., which preprocessing steps need to be done) into the config, load them as critical parameters, and then have that be the only point of configuration for the preprocessing.
The text was updated successfully, but these errors were encountered: