Opened 13 years ago
Closed 13 years ago
#273 closed enhancement (fixed)
Add tests that instantiate ERFs and call updateForecast()
Reported by: | Peter Powers | Owned by: | Peter Powers |
---|---|---|---|
Priority: | major | Milestone: | OpenSHA 1.2 |
Component: | sha | Version: | |
Keywords: | Cc: |
Description
This is one of several easy to implement baseline tests that will improve routine monitoring of the project.
Change History (2)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
WG_02 has been fixed and a switch added to cathc the other four ERFs that fail due to a lack of user input when updateForecast() is called.
Note: See
TracTickets for help on using
tickets.
OK I created a test in trunk/test/org/opensha/sha/earthquake/rupForecastImpl/ProductionERFsInstantiationTest.java. Here is the criteria:
Tests the following criteria for each DevStatus?.PRODUCTION ERF.
If the erf is a regular ERF the following criteria is checked:
If the erf is an EpistemicListERF the following criteria is checked:
Unfortunately, of the 22 current production ERFs, there is 1 failure and 4 errors. Here are the failures:
This sort of test doesn't really apply to the PEER & Poisson fault ERFs since they require the user (or a control panel) to set parameters. Should we create some sort of tagging interface, or maybe a boolean in ERF_Ref for differentiating between ERFs that are self-sufficient, and those that aren't?
Leaving this open until these issues are resolved.