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
It appears that a recent PolicyBrain update broke old CCC links. I should be able to go to ospc.org/ccc/800, for example, and see results, but instead I get a 500 internal server error. Similarly, I should be able to go to http://www.ospc.org/ccc/edit/800/ and see the parameter changes that resulted in ospc.org/ccc/800.
We do not need to ensure that users can re-run old simulations, but they should be able to see their results, the inputs that generated, and the version of PolicyBrain that they used. With this information and some work, it should be possible to replicate analyses locally.
Whether or not it is possible to fix this problem now, we should have some tests that protect links in the future and to document that this is a PolicyBrain requirement.
The text was updated successfully, but these errors were encountered:
MattHJensen
changed the title
Broken PolicyBrain input/output links
Broken PolicyBrain links
Oct 10, 2017
MattHJensen
changed the title
Broken PolicyBrain links
Broken PolicyBrain prior-run links
Oct 10, 2017
It looks like this capability works back to run 877 which occurred on the same day as PolicyBrain release 1.0.3. This was the release where we started using the bokeh plot for the CCC. B-Tax had to be updated in order to return the required data for this plot. Thus, when we try to load an earlier CCC run, we are unable to parse the results.
It appears that a recent PolicyBrain update broke old CCC links. I should be able to go to ospc.org/ccc/800, for example, and see results, but instead I get a 500 internal server error. Similarly, I should be able to go to http://www.ospc.org/ccc/edit/800/ and see the parameter changes that resulted in ospc.org/ccc/800.
We do not need to ensure that users can re-run old simulations, but they should be able to see their results, the inputs that generated, and the version of PolicyBrain that they used. With this information and some work, it should be possible to replicate analyses locally.
Whether or not it is possible to fix this problem now, we should have some tests that protect links in the future and to document that this is a PolicyBrain requirement.
The text was updated successfully, but these errors were encountered: