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
amr_to_string appears to change data as its being read. This means that a test case (AMR.amr_to_string(AMR.load(ASKEModel, model_expr))) == modelrep will always fail. Here are two concrete observations of this issue:
"@" character is omitted on AMR.load Expected Call the argument of amr_to_string in the test case M. A substring of M.header should read:
"...ASKE Model Representation: SIR [email protected]..." Observed The substring of M.header omits the "@" character:
"...ASKE Model Representation: SIR Model0.1..."
A match case in amr_to_string erroneously interprets ODERecord as ODEList Expected The ODERecord is interpreted by the ODERecord match case and return "ODE_Record = ..." Observed The relevant substring in the output of amr_to_string has "ODE Equations" instead.
The text was updated successfully, but these errors were encountered:
amr_to_string appears to change data as its being read. This means that a test case
(AMR.amr_to_string(AMR.load(ASKEModel, model_expr))) == modelrep
will always fail. Here are two concrete observations of this issue:AMR.load
Expected Call the argument of
amr_to_string
in the test caseM
. A substring ofM.header
should read:"...ASKE Model Representation: SIR [email protected]..."
Observed The substring of
M.header
omits the "@" character:"...ASKE Model Representation: SIR Model0.1..."
amr_to_string
erroneously interpretsODERecord
asODEList
Expected The
ODERecord
is interpreted by theODERecord
match case and return "ODE_Record = ..."Observed The relevant substring in the output of
amr_to_string
has "ODE Equations" instead.The text was updated successfully, but these errors were encountered: