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
If there's a problem with the CondPriority or CondTag values, we should see an error, but the logs (in NRMC at least and presumably from the Oasis API) end with RUNNING: oasislmf.preparation.il_inputs.get_il_input_items and lack any specific error message. This makes it difficult to know what went wrong and what needs changing.
If we run oasislmf exposure run or an MDK analysis then we see the error (although it's not labelled clearly as an error).
Steps to Reproduce (Bugs only)
Create a portfolio with mismatched CondTags (included below).
Confirm that oasislmf exposure run flags an error on this file.
Output from oasislmf exposure run: error is shown (but there is no clear mention that this is an error).
...
RUNNING: oasislmf.preparation.il_inputs.get_il_input_items
Those condtag are present in locations but missing in the account file:
PortNumber AccNumber CondTag
1 1 1 tag2
Running via the MDK also shows the message.
...
2024-12-03 18:33:04,691 [INFO] RUNNING: oasislmf.preparation.il_inputs.get_il_input_items
Those condtag are present in locations but missing in the account file:
PortNumber AccNumber CondTag
1 1 1 tag2
2024-12-03 18:33:14,810 [ERROR] Those condtag are present in locations but missing in the account file:
PortNumber AccNumber CondTag
1 1 1 tag2
ERROR: OasisLMF produced no results - see log output.
But running in NRMC, the analysis_*.log file ends without including the message.
Issue Description
If there's a problem with the
CondPriority
orCondTag
values, we should see an error, but the logs (in NRMC at least and presumably from the Oasis API) end withRUNNING: oasislmf.preparation.il_inputs.get_il_input_items
and lack any specific error message. This makes it difficult to know what went wrong and what needs changing.If we run
oasislmf exposure run
or an MDK analysis then we see the error (although it's not labelled clearly as an error).Steps to Reproduce (Bugs only)
oasislmf exposure run
flags an error on this file.Version / Environment information
Example data / logs
portfolio.zip
Output from
oasislmf exposure run
: error is shown (but there is no clear mention that this is an error).Running via the MDK also shows the message.
But running in NRMC, the
analysis_*.log
file ends without including the message.The text was updated successfully, but these errors were encountered: