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
When I download and run the Windows 64-bit version of the latest 0.9.0 Pareto UI and try the default scenario (Strategic Permian Demo), using all defaults in Optimization Setup and not adding any data inputs, I get the following error
I probably had an earlier version installed, but I think that is a normal situation so even if that's the cause, it's still a bug.
The text was updated successfully, but these errors were encountered:
I'm thinking this is occurred for one of 2 reasons. Either the input excel sheet used was an older version, or the up-to-date input excel sheets have been updated since the 0.9.0 release. Due to the nature of how we read the data in from the excel sheets (by reading all tabs at once), if the UI isn't updated accordingly with the excel sheets, the function to read the data usually fails.
@dangunter with a fresh install of the UI this morning, I am also getting an error, but it's different than the error you are seeing:
The cause of this error is known - it's because of this PR which merged yesterday and changed the way that one of the parameters is indexed (parameter p_delta_Disposal which corresponds to spreadsheet tab "DisposalCapacityIncrements"). This error should be resolved once we build a version of the UI with the latest version of the backend.
As for the error message you saw Dan, I am not sure why that would have happened. The latest version of strategic_permian_demo.xlsx does have a worksheet named "ROA", although there is not any data in that worksheet:
When I download and run the Windows 64-bit version of the latest 0.9.0 Pareto UI and try the default scenario (Strategic Permian Demo), using all defaults in Optimization Setup and not adding any data inputs, I get the following error
I probably had an earlier version installed, but I think that is a normal situation so even if that's the cause, it's still a bug.
The text was updated successfully, but these errors were encountered: