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 there any particular reason Cumulus 3/MX reverted to Cumulus 1s approach of "whatever units you set initially are how the data will be stored", as opposed to Cumulus 2s approach which allowed you to change units at any time? When I initially set up Cumulus I set the wind units to kts, and only later realised that, to change to mph, I would have to manually convert all of the data (and as such I've just lived with it since).
The text was updated successfully, but these errors were encountered:
MX was created long before I took over maintenance of it. It is basically a port of Cumulus 1 to the MS .Net framework so adopted all of C1's characteristics.
Is there any particular reason Cumulus 3/MX reverted to Cumulus 1s approach of "whatever units you set initially are how the data will be stored", as opposed to Cumulus 2s approach which allowed you to change units at any time? When I initially set up Cumulus I set the wind units to kts, and only later realised that, to change to mph, I would have to manually convert all of the data (and as such I've just lived with it since).
The text was updated successfully, but these errors were encountered: