search

sjrwmd-wmm / nfseg_auto_cup_tool

This repository hosts the District's Regulatory automated tool to calculate changes in groundwater availability and other drawdown effects due to well additions or deletions (cup - consumptive use permit) within the NFSEG groundwater model.
0 stars 0 forks source link

Documentation updates #17

Closed pbremner-sjr closed 3 years ago

pbremner-sjr commented 3 years ago
  1. Make sure it’s clear to the user that the testing tool needs to be located on a drive that is mapped on the computer, not just from a server. (ex. Does not run from \poseidon, but will run from E: drive that is mapped to poseidon).
  2. Explain in the guide that you can type “input_user_files\”name of csv you’re running” in the command line when it asks for the name of the file.
  3. Make clear in the documentation the location of the output results directory. There were suggestions to move this directory to a location within the reg tool folder, although the reg tool will be continually updated which would overwrite the existing tool in your working directory.
  4. Cleanup README files located in tool directories. Some of these are outdated, or contain information specific to scripts.
  5. Include information about README.md "markdown" file that is downloaded with the tool in the documentation.
  6. Include some description in the documentation to know setup batch file was successful. The py_path_autogen text file should be created and it should not be empty. The model_update.zip should be unzipped into a folder named "model_update".
  7. Add text describing error that is seen on the command line when an XY well is added that is outside of the model grid. This can results in a trackback message that the results are dividing by zero. Description should be added that the NFSEG grid should be referenced before adding in a new well.
  8. Include that the layer dh_layerX in the dh.mxd may need to be rescaled to symbolize all values calculated by the model run. Some cells show up as "blank" or unclassified in the map because they are outside of the range.
  9. Make note that the dh_layerX is semi-transparent to enable the user to add base maps or reference layers.

Original issue opened Oct 19, 2020 by @lmeridth

pbremner-sjr commented 3 years ago

Progress made with commit d6ae16e

Original comment made on Oct 26, 2020 by @lmeridth

pbremner-sjr commented 3 years ago

This issue is completed and can be closed.

Original comment made on Oct 26, 2020 by @lmeridth