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
Is your feature request related to a problem? Please describe.
Currently we are saving aydin.it level objects when we save a trained model. This is working out well so far but it will be a bigger convenience if we can switch to aydin.restoration level objects. That way, we can incorporate selections on specific pre/post-processing options as well. Also this will help us to simplify some of the GUI and CLI related code pieces. Important to note: This will be a breaking change and users will not be able to use their previously trained models on the earlier versions of Aydin. We are promoting use of restoration level API, we use restoration level API both on CLI and GUI ourselves. We can make our saved models compatible at restoration level API too.
Describe the solution you'd like
Moving the business logic in aydin.it.base to aydin.restoration.denoise.base or maybe somewhere else to comfort deconvolution restorations too.
Describe alternatives you've considered
An alternative could be not making such breaking change but as we want to implement further features regarding saving/loading models, it only introduces more complications due to nature of our client code(which tries to stick to restoration level API).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently we are saving
aydin.it
level objects when we save a trained model. This is working out well so far but it will be a bigger convenience if we can switch toaydin.restoration
level objects. That way, we can incorporate selections on specific pre/post-processing options as well. Also this will help us to simplify some of the GUI and CLI related code pieces. Important to note: This will be a breaking change and users will not be able to use their previously trained models on the earlier versions of Aydin. We are promoting use of restoration level API, we use restoration level API both on CLI and GUI ourselves. We can make our saved models compatible at restoration level API too.Describe the solution you'd like
Moving the business logic in
aydin.it.base
toaydin.restoration.denoise.base
or maybe somewhere else to comfort deconvolution restorations too.Describe alternatives you've considered
An alternative could be not making such breaking change but as we want to implement further features regarding saving/loading models, it only introduces more complications due to nature of our client code(which tries to stick to restoration level API).
The text was updated successfully, but these errors were encountered: