Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulation result files and input files #319

Closed
chraibi opened this issue Jul 11, 2019 · 4 comments
Closed

Simulation result files and input files #319

chraibi opened this issue Jul 11, 2019 · 4 comments
Assignees

Comments

@chraibi
Copy link
Contributor

chraibi commented Jul 11, 2019

In Gitlab by @gjaeger on Jul 4, 2019, 08:06 [origin]

jpscore:

JuPedSim - JPScore

Current date   : Jul  2 2019 19:07:41
Version        : 0.8.4
Commit hash    : v0.8.4-68-ga33375a
Commit date    : Mon Jul 1 15:21:05 2019
Branch         : develop
----

inifile in /data:

<header>
  <seed>4313</seed>
  <max_sim_time>80</max_sim_time>
  <num_threads>48</num_threads>
  <show_statistics>true</show_statistics>
  <logfile>log_RiMEA_Test_04_7-0_om_2</logfile>
  <!--<progressbar/>-->
  <trajectories format="plain" fps="2">
    <file location="traj_RiMEA_Test_04_7-0_om_2.txt" />
  </trajectories>

  <geometry>geo_RiMEA_Test_04.xml</geometry>
</header>

...

batch_script in $HOME:

#!/bin/bash -x
#SBATCH -J R70
#SBATCH --account=ias-7
#SBATCH --nodes=1
#SBATCH --ntasks=1
#SBATCH --cpus-per-task=48
#SBATCH --output=data/out_%j.txt
#SBATCH --error=data/err_%j.txt
#SBATCH --time=6:00:00
#SBATCH --mail-user=g.jaeger@fz-juelich.de
#SBATCH --mail-type=ALL

export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK}

srun ./jpscore/bin/jpscore data/ini_RiMEA_Test_04_7-0_om_2.xml

The logfile is stored in the root directory ($HOME) as datalog_RiMEA_Test_04_7-0_om_2.txt. Also the statistic files are stored there.

Both files should be stored in the directory data (like the trajectory files).

Note:
The function <progressbar/> creates a very large file (5-15 GB) and should be disabled.

@chraibi chraibi self-assigned this Jul 17, 2019
@anna-braun
Copy link
Contributor

anna-braun commented Aug 2, 2019

I started a simulation with Jureca today and I have a similar problem. The Trajectories have been written to the directory "Simulationen/test-01", but the statistic files and goal.vtk have been written to the root directory:
Bildschirmfoto 2019-08-02 um 13 31 16

@chraibi @schroedtert Is there any possibility to set a file location to "show_statistics"? If not, we should really add this function. For the KapaKrit simulations we will have many statistic files (100+/simulation), which will lead to total chaos, if all the files will be be written into the same/root directory.

batch.sh.txt

@chraibi chraibi changed the title JURECA | header, logfile Auxilliary files direction (log-file, statistics-files) Aug 4, 2019
@chraibi
Copy link
Contributor Author

chraibi commented Aug 4, 2019

During the process of fixing #448, I would propose to save these files (log and flow*) in the same directory as the trajectory file.

Screenshot 2019-08-04 23 20 40

@zeroset zeroset changed the title Auxilliary files direction (log-file, statistics-files) Simulation result files and input files Dec 16, 2019
@zeroset zeroset assigned zeroset and unassigned chraibi Dec 16, 2019
@anna-braun anna-braun pinned this issue Dec 18, 2019
@anna-braun
Copy link
Contributor

@zeroset

  1. As discussed today the structure for the output could look like this:
    Datenstruktur
    With an new output folder for every simulation, which contains all output files like trajectory files and flow statistics and a copy of all input files.
  2. Also important is the paths in the trajectory file. At the moment these are absolute paths:
    Pfade_ist
    But it should better be relative paths to have more flexibility when changing a folders name or sharing the data.
    Pfade_soll

@schroedtert
Copy link
Contributor

Can this be closed? See #649

@zeroset zeroset closed this as completed Feb 3, 2020
@anna-braun anna-braun unpinned this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants