Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • hru-delin hru-delin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

En prévision de l'arrivée de la forge institutionnelle INRAE, nous vous invitons à créer vos nouveaux projets sur la forge MIA.

  • hru-delin-devhru-delin-dev
  • hru-delinhru-delin
  • Wiki
  • Home

Home · Changes

Page history
Update home authored 4 years ago by Veyssier Julien's avatar Veyssier Julien
Hide whitespace changes
Inline Side-by-side
Showing
with 21 additions and 0 deletions
+21 -0
home.md
View page @ 85b1aa05
......@@ -50,6 +50,8 @@ pip3 install --user pandas dbf tqdm
## HRU delin
Installing hru-delin on your machine is pretty simple. There is no need to install it on the system.
Get the release archive and extract it somewhere. Then make sure the `bin` directory is in your `PATH` environment variable. Here is an example procedure:
``` bash
# go to your home directory
......@@ -91,6 +93,25 @@ If you name your config file `hrudelin_config.cfg`, and you're placed in the sam
hru-delin_all-steps.sh
```
## Intermediate
### Multiple config files for one dataset
If you want to try multiple options and configuration for the same dataset, there is no need to duplicate the data set (specially if it's big). You can write multiple .cfg files that use this dataset.
**Be carefull** to write the results in different places/directories to make sure you don't loose track of what is produced by your different runs.
### Start a run from partial results
If someone successfully ran step1 and step2 but wants to run step3 and step4 on another machine because it requires more CPU power, it is perfectly possible. The only directory that one needs to copy with the dataset is the intermediate results directory.
```
[dir_out]
files:my_intermediate_results
```
No need to copy `grass_db` and `tmp` directories.
On the destination machine, just run step3 and it will use intermediate results.
## Advanced
### Working directory
......
Clone repository
  • Home

Menu

Explore Projects Groups Topics Snippets