Closed rmscheller closed 7 years ago
Will do. Within SCRAPPLE -> Phase_1 -> examples there are example files (including ignition input maps) that I will update and move over to the Test Runs folder
Let's set up a separate directory for each test.
I added the first (severity = 1) damage to the input file and updated the RunsToCompletion test. Let's discuss testing efficiency next meeting. Maybe I should always run this one after each day of programming; more specific tests for you.
Yes I think it would be most efficient for me to take any tests related to model behavior and leave yours more general
OK. I'll try to get it set up.
I included a set of Lake Tahoe inputs under 'LTW_NECN_H'. It has scrapple input ignitions maps but I don't think they've been tested yet. I've been running spatial ignitions test out of 'RunsToCompletion' but maybe I should set up a NECN_H test directory for that too?
Yes, let's set up pretty fine-grained test folders, explicitly named. So move to Test_SpatialIgnitions, for example.
For 99x99 cell test landscapes, it seem like ignition parameters B0=-5, B1=0.05 produces a fairly reasonable number of fire for such a small landscape
I began to set up a basic "run to completion" test which should indicate whether the extension is capable of running to completion. It needs appropriate inputs, notably maps.
We will also need more specific tests which are compared against R. For example, given B0 and B1, does it produce the appropriate number of Lightning/Rx/Accidental ('LAR' for short) fires?