1 / 20

Utilities

Utilities. So, normally one will work with simulation parameter files by launching the CS Explorer program. CropSyst simulations require a number of files that store the parameters that control and adjust the various submodels in the CropSyst model.

mcdowellj
Download Presentation

Utilities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Utilities

  2. So, normally one will work with simulation parameter files by launching the CS Explorer program. CropSyst simulations require a number of files that store the parameters that control and adjust the various submodels in the CropSyst model. CS Explorer implements most of the functions in Windows Explorer for the basic file management.

  3. Additional buttons are provided to: Edit a selected file in notepad. (If no file is selected, open the notes.txt)

  4. Additional buttons are provided to: Launch another CS Explorer window open to the current folder.

  5. Additional buttons are provided to: Launch Windows Explorer open to the current folder.

  6. Additional buttons are provided to: Open Windows/DOS console in the current folder.

  7. Context functions panel CS Explorer provides in the lower panel, various functions that are available for working with files and directories with respect to specialized CropSyst directory contexts.

  8. Position of primary functions Input fields, and buttons that perform specific functions are organized with the primary and/or most frequently performed operations positioned at the top of the panel with optional functions listed lower in the panel.

  9. Positionion of secondary/optional functions Secondary and optional functions are listed lower in the panel.

  10. Arbitrary directory Initially there is no recognized directory structure, so CS explorer will display the functions for a normal arbitrary directory context.

  11. Standard directory structure CS explorer suggests a special directory structure to organize CropSyst parameter files. You do not have to use this directory structure.

  12. Personalized directory structure Indeed if you have a complicated set of simulation scenarios and parameter files, then some other directory structure may be more suitable. 

  13. Arbitrary directory You can use the file manager can create any directory structure to organize your projects and parameter files. The "Assume context:" with "[]Permanently" checkbox and the directory context selection box can be used to force CS explorer to recognize the current directory as a specialized CropSyst context (not all context types can be permanently affixed).

  14. Create a simulation directory You can start creating projects in any arbitrary directory, however I usually create a "Simulation" directory either in my documents folder or the root drive of the hard disk.

  15. Create a simulation directory You can start creating projects in any arbitrary directory, however I usually create a "Simulation" directory either in my documents folder or the root drive of the hard disk. The optional "Create simulation folder" function button will set up the default initial directory structure in the current arbitrary directory. 

  16. Creating projects directories for simulations The created simulation directory and projects subdirectory can be any name you want. Default names in various languages are provided in the drop down box.

  17. Parameter database levels CropSyst parameter editors recognize three levels of parameter database directories: Master simulation, Project and Scenario. In the Master level database, one would store parameter files that would be commonly shared by multiple projects (frequently used soil and weather files are commonly stored in master level databases). Parameter files that will be used by multiple scenarios in a project will be often stored in the project level database.  Files that will only be used by a specific scenario would be stored in the scenario's database. Most often, parameter files will be stored in the project level database.

  18. Creation of simulation components Most directory contexts provide a function to create a new file in the folder. Simply enter the name in the input field and press the "Create" button. The checkbox "[]Automatically go into created context folders" will set the file list to view the created folder.

  19. Project context A project is simply a directory which stores a set of scenarios, often a parameter file database directory and a set of parameter files for various optional simulation modules (GIS simulation, Grazing regimens). The “Goto project: Scenarios and Database” buttons will move the view to the respective directory context (if it doesn't already exist, then the directory will be created ). For advanced users, there is a facility to generate scenarios. We will not cover that in this course.

  20. Database context Parameter files for soil, weather, crop, management, and rotation, can either be first created in a parameter database directory, and then selected to define a scenario in a "bottom up" manner. Or you can create a scenario first and create/select parameter files as needed in a "top down manner" In either case you may find it more convenient to first create the "project level" "database directory". Then, in this directory, add the subdirectories for the various types of parameter files that would be used in the project.

More Related