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 reason for this happening is that calling RampModel(model) creates a shallow clone of model, which doesn't copy arrays (that can be seen adding this to the above example {}assert m.data is ramp_from_lvl1b.data{}). This behavior is at least 6 years old and is documented as intended (see the description of the "shallow copy" here 6ff2a48a7018f45d5afa5e279924cab6f1c5eefb])
However, since the pipeline uses RampModel(some_level1b_model) quite often, it can lead to the crash due to different data types. The recommendation would be to override RampModel.clone (or maybe the {}*_init_*{}) to cast the arrays to the new dtypes.
The text was updated successfully, but these errors were encountered:
Issue JP-3826 was created on JIRA by Maria Pena-Guerrero:
When converting a datamodel of type Level1b to RampModel, the data type does not covert from integer to float. If a user does
The reason for this happening is that calling
RampModel(model)
creates a shallow clone of model, which doesn't copy arrays (that can be seen adding this to the above example{}assert m.data is ramp_from_lvl1b.data{
}). This behavior is at least 6 years old and is documented as intended (see the description of the "shallow copy" here 6ff2a48a7018f45d5afa5e279924cab6f1c5eefb])However, since the pipeline uses
RampModel(some_level1b_model)
quite often, it can lead to the crash due to different data types. The recommendation would be to overrideRampModel.clone
(or maybe the{}*_init_*{
}) to cast the arrays to the new dtypes.The text was updated successfully, but these errors were encountered: