Closed lucadelu closed 6 months ago
The temp_force_dir
is used by sadasadam to store intermediate FORCE results in a specific folder with a timestamp (in the example above: scratch3/delucchil/sadasadam/temp_force/force_dir_20231122_115245
). Data stored there are for example the whole level-2 FORCE datacube and the FORCE mosaics.
Error: Output is incomplete. Cannot append to buffer file in /tmp. Is the disk full? parallel: Error: Change $TMPDIR with --tmpdir or use --compress
--> It may be that FORCE itself uses the /tmp
directory to store some further temporary data during processing. Maybe setting the $TMPDIR
env variable helps?
If the data has not been cleaned up (or if you used remove_force_data: False
), you could also check the data in /scratch3/delucchil/sadasadam/temp_force/force_dir_20231122_115245/level2
as well as the FORCE log files.
This issue seems to be related to the GNU parallel usage of FORCE level-2 processing. I found a similar issue (unrelated to FORCE) here. I am not sure whether the issue lies in sadasadam or FORCE itself. If you still have the downloaded data, you can try to directly run the FORCE command instead of sadasadam to isolate the problem further, for this you would need to define a FORCE parameter file.
The
temp_force_dir
is used by sadasadam to store intermediate FORCE results in a specific folder with a timestamp (in the example above:scratch3/delucchil/sadasadam/temp_force/force_dir_20231122_115245
). Data stored there are for example the whole level-2 FORCE datacube and the FORCE mosaics.
Error: Output is incomplete. Cannot append to buffer file in /tmp. Is the disk full? parallel: Error: Change $TMPDIR with --tmpdir or use --compress
--> It may be that FORCE itself uses the/tmp
directory to store some further temporary data during processing. Maybe setting the$TMPDIR
env variable helps?
ok, I run it in a different blade and the error didn't appear so probably the issue of full disk was not related to me, however to be sure I'll try to set different $TMPDIR
env variable
If the data has not been cleaned up (or if you used
remove_force_data: False
), you could also check the data in/scratch3/delucchil/sadasadam/temp_force/force_dir_20231122_115245/level2
as well as the FORCE log files.This issue seems to be related to the GNU parallel usage of FORCE level-2 processing. I found a similar issue (unrelated to FORCE) here. I am not sure whether the issue lies in sadasadam or FORCE itself. If you still have the downloaded data, you can try to directly run the FORCE command instead of sadasadam to isolate the problem further, for this you would need to define a FORCE parameter file.
ok, I could try, however now it is running but I have other errors, I'll report tomorrow new issues.
For now we can keep this issue open but nothing to do, thanks
I got an error during FORCE processing related to temporary directory, it seems to write into
/tmp/
but in my config.yml file I settemp_force_dir: '/scratch3/delucchil/sadasadam/temp_force/'
(/scratch3/ has some free TB)