The progress bar that is output by PARM takes up a lot of space when piped to a text file (which commonly happens when running in a pipline or other scheduling software).
Would suggest to replace the progress bar for a more efficient solution. E.g. printing plain text progress every 5% or so.
As an example, the following output takes up a whopping 5.2Mb of disk space:
14%|███▉ | 555512/4095477 [1:56:26<12:22:08, 79.50it/s]foo@bar.com: /foo/bar
cat .command.log
██████╗ █████╗ ██████╗ ███╗ ███╗
██╔══██╗██╔══██╗██╔══██╗████╗ ████║
██████╔╝███████║██████╔╝██╔████╔██║
██╔═══╝ ██╔══██║██╔══██╗██║╚██╔╝██║
██║ ██║ ██║██║ ██║██║ ╚═╝ ██║
╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝
Promoter Activity Regulatory Model
Version: 0.1.44
================================================================================
Predict
--------------------------------------------------------------------------------
Model: /foo/
Input: foo.fa
Output: foo_parm.txt
Number of batches: 1
Show only sequence's header in the output file?: False
Model filter size : 125
Loss function type: poisson
L_max: 600
Predict test fold?: False
================================================================================
[PARM v0.1.44] Loading models
[PARM v0.1.44] Found 1 model files in /foo/bar/
[PARM v0.1.44] Making predictions
[PARM v0.1.44] Total sequences: 4095477
14%|███▉ | 556326/4095477 [1:56:36<11:52:45, 82.76it/s]
The progress bar that is output by PARM takes up a lot of space when piped to a text file (which commonly happens when running in a pipline or other scheduling software).
Would suggest to replace the progress bar for a more efficient solution. E.g. printing plain text progress every 5% or so.
As an example, the following output takes up a whopping 5.2Mb of disk space: