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
The current implementation of compound models essentially replicate all parameter instances at every level of the expression tree. This effectively results in the number of parameter instances increasing roughly with the square of the number of class instances times (assuming roughly even distribution of parameters with model instances). This is not an idle worry. Some JWST WCS models involve nearly 100 model components and almost 300 parameters. This leads to over 10 thousand parameter instances and huge memory usage, and consequent time instantiating the model (significant fractions of an hour for MOS cases). This basically renders the current implementation impractical for such complex models.
One could try to optimize this with the existing implementation, but there is no simple way to make the user interface transparent if python expressions are to be used to create compound models. I have tried an alternate implementation of compound models that I will submit a PR soon for comments.
The text was updated successfully, but these errors were encountered:
The current implementation of compound models essentially replicate all parameter instances at every level of the expression tree. This effectively results in the number of parameter instances increasing roughly with the square of the number of class instances times (assuming roughly even distribution of parameters with model instances). This is not an idle worry. Some JWST WCS models involve nearly 100 model components and almost 300 parameters. This leads to over 10 thousand parameter instances and huge memory usage, and consequent time instantiating the model (significant fractions of an hour for MOS cases). This basically renders the current implementation impractical for such complex models.
One could try to optimize this with the existing implementation, but there is no simple way to make the user interface transparent if python expressions are to be used to create compound models. I have tried an alternate implementation of compound models that I will submit a PR soon for comments.
The text was updated successfully, but these errors were encountered: