HOW TO visualise 'wells running dry'

This page explains step by step how to how to visualise 'wells running dry'

Step 1: Check GA output file XXX_output.in

1. Check if the parameter QSRC_GW is listed in BINARY_MAPSTACKS *MERGE* in the GA output file located in the modules folder
2. Check if QSRC_GW is listed in wells_out for merged layer (WELLS_OUT 'QSRC_GW' NO_NAME_CHECK *MERGE*)

Step 2: Update module instance spreadheet

For visualising 'wells running dry' a few adjustments had to be made in the module instance spreadsheet. You can look at the NGMS module instance generator spreadsheet as an examplefrom wher you can copy the things needed (take care that you adjust the model name, location name, etc...). Following things have to be done

1. add the sheet diff_sim_inp to your spreadsheet
2. sheet runMF:
   • change location set for import of QSRC_GW from file XXX_QSRC_GW_TimeSeries.xml from XXX_wells_all to XXX_wells_singles_and_childs
   • add import of QSRC_GW from file XXX_QSRC_GW_TimeSeries_MultiLayer.xml for XXX_wells_parents
   • check if QSRC_GW from file XXX_QSRC_GW_merged_MapStacks.xml is imported for the merged grid
3.  

Step 1: Check xxx_global.properties

1. Make sure that the global properties include the following line: USE_CURRENT_SIMULATED_WITH_COLD_STATE_SELECTION=true

Step 2: Check locations in LocationSets.xml

1. Make sure that the order of the location sets in location set xxx_wells_parents is as follows:
   1)  WMW_wells_normal_parents
   2)  WMW_wells_super_parents
   
2. Make sure all locations which refer to super parents are childs or normal parents (no singles!)
3. Update locations spreadsheet

Step 3 Check IdMapping

1. comment the shut down activity in the GA run out for all scenarios
2. run the model
3. check for each scenario if the id's in WMW_QSRC_GW_TimeSeries_MultiLayer.xml and WMW_QSRC_GW_TimeSeries.xml in the toNGMS modules folder are the same as listed in the idmapping (Config/IdMapFiles), especially check the ordering of layers in the name of the super / normal parents
4. if the id's are not the same you have to update the id mapping (see also pages 'HOW TO add a new module' #Step 4.8. Obtain configuration data via Module Adapter and Go to #Step 5.9. IdMaps for GW abstraction), therefore
   • run the the xxx_prepare.but for each scenario-type in the modules directory
   • populate the location worksheets as follows
     • #**# copy the individual locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations.xml  
       1. paste into column H,I,J,K (starting at row 3)
       2. copy the parent locations (id, x,y,z) as listed in XXX_GW_abstractions_Locations_MultiLayer.xml
       3. paste into column B,C,D,E (starting at row 3)
       4. check that the format of z coordinatecomment the shut down activity in the GA run ou
       5. Create a backup with name XXX_LocationsResults_versionnumber.xls
       6. Run the macro 'create_XMLfiles'
       7. The macro creates XML-files in the directory of the data-spreadshee
       8. The macro overwrites existing files
       9. You can skip location types to be generated
       10. Check the contents of the id map files. It might be wise to validate with an XML-validation tool.
       11. Copy the id map files which are OK to your configuration --> \Config\IdMapfiles
5. enable the shut down activity in the GA run

Step 3