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 found some weird situations in which all negative values of one submodel are ignored without any warning or error. This is the smallest model I found where this happens:
Has there been any update on this sub-model+negative values bug?
We're also running into issues where negative values are ignored for some parameters but only if sub-models are used.
If no sub-models are used then the negative values are correctly output for all parameters.
It seems like when the bug happens even explicitly defined combinations in the seed file are excluded from the output.
For example:
./pict test.pict /e:seed.txt /o:1
test.pict
D1: 1, ~0
D2: 1, ~0
D3: 1, ~0
C1: 1, 2, ~0
C2: 1, 2, ~0
# no issue if you comment out the sub-models below
{C1, C2}
{D1, D2, D3}
I found some weird situations in which all negative values of one submodel are ignored without any warning or error. This is the smallest model I found where this happens:
Current Behavior:
pict model /r:1222
Expected Behavior:
C1=~0
C2=~0
The text was updated successfully, but these errors were encountered: