You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the PRINT_FLOW option is activated, might we also consider incorporating the package name within the output? This enhancement would notably facilitate the extraction of flow results utilizing tools such as grep.
For instance, envisioning a DRN output:
DRN PACKAGE (HATCHERY) FLOW RATES PERIOD 191 STEP 1
NUMBER
CELLID
RATE
1
(1,277,124)
0.0000000
could undergo transformation to:
DRN PACKAGE
FLOW RATES
PERIOD
STEP
PACKAGE
NUMBER
CELLID
RATE
(HATCHERY)
DRN
191
1
HATCHERY
1
(1,277,124)
0.0000000
This adjustment would enable me to utilize grep "^ HATCHERY" output.lst > drn.lst. Alternatively, we could explore the feasibility of introducing another option that would allow us to export flows to a CSV format.
The text was updated successfully, but these errors were encountered:
When the PRINT_FLOW option is activated, might we also consider incorporating the package name within the output? This enhancement would notably facilitate the extraction of flow results utilizing tools such as grep.
For instance, envisioning a DRN output:
DRN PACKAGE (HATCHERY) FLOW RATES PERIOD 191 STEP 1
could undergo transformation to:
This adjustment would enable me to utilize grep "^ HATCHERY" output.lst > drn.lst. Alternatively, we could explore the feasibility of introducing another option that would allow us to export flows to a CSV format.
The text was updated successfully, but these errors were encountered: