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
In the first step of the analysis type, we need to determine whether we are running audio2csv or not. Importantly that name (audio2csv) should never be shown to the user.
The decision to run audio2csv or not is based on the length of the file.
I suggest this workflow (wording could use some improvement):
How long are your files?
"Is each file longer than 5 minutes long?" ➡ then choose audio2csv
"Is each file less than 5 minutes long?" ➡ do not use audio2csv
If audio2csv then list available analyses as returned by AnalysisPrograms.exe analysesavailable
since everything returned by analysesavailable can be run from audio2csv we can safely run all these variants
If NOT audio2csv then list some other commands (e.g. audio2sonogram, and the others you have in the UI)
You can leave these choices as not-implemented ("Coming Soon") just as they are now
related work:
in AP.exe more CLI work (e.g. a command to list non-IAnalyzer commands) to use for step 3 above
in AP.exe fix-up descriptions etc
The text was updated successfully, but these errors were encountered:
In the first step of the analysis type, we need to determine whether we are running
audio2csv
or not. Importantly that name (audio2csv
) should never be shown to the user.The decision to run audio2csv or not is based on the length of the file.
I suggest this workflow (wording could use some improvement):
AnalysisPrograms.exe analysesavailable
analysesavailable
can be run from audio2csv we can safely run all these variantsThe text was updated successfully, but these errors were encountered: