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
I just noticed that backwards compatibility was broken once TRestAxionSolarFlux was promoted to pure abstract class. Because when trying to read a previous version (before 2.4.0) it tries to instantiate a TRestAxionSolarFlux. But now this class is pure virtual.
I don't think there is anything we can do to solve that. Just reading v2.3.15 generated axion data with v2.3.15.
Personally, my problem is that I have to regenerate the data using v2.4.0 to exploit the new features added in TRestDataSet.
invalidThis doesn't seem rightnewsSomething you think should be shared with the community (even if not crucial)good-to-knowSomething crucial you think should be shared with the community
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
REST-for-Physics
-
I just noticed that backwards compatibility was broken once
TRestAxionSolarFluxwas promoted to pure abstract class. Because when trying to read a previous version (before 2.4.0) it tries to instantiate aTRestAxionSolarFlux. But now this class is pure virtual.I don't think there is anything we can do to solve that. Just reading v2.3.15 generated axion data with v2.3.15.
Personally, my problem is that I have to regenerate the data using v2.4.0 to exploit the new features added in
TRestDataSet.Any insights or complains are welcome!
@rest-for-physics/axionlib
Beta Was this translation helpful? Give feedback.
All reactions