Hello -
At the conclusion of running the Analysis step, I want to now manually verify a portion of the results. I click on the ‘Start’ button under Step 3: Annotation, and I get a message popup that the JSON file is very large (68.06 MB) and that the verification step will be slow. I click OK and nothing happens. I’ve been waiting for a half hour, and still nothing has happened. I don’t really want to skip this step, as there are a few species of interest that look very similar and have been mixed up by the recognizer in the past.
If I skip this step now and go ahead to post-processing, can I re-open this analysis result and manually verify results later?
Not sure what is going on with your install, but it seems like there are errors popping up that I haven’t seen before.
Are you by any chance running it on a locked down machine with loads of security software (like common for universities and government agencies)? That has resulted in weird behaviour in the past, which was usually resolved with a manual install.
To give me some more information on what’s going on, you might want to rerun this error in debug mode. That will provide me with the full output instead of only the error trace.
I’ve actually run into the same issue. First time running through a folder, I got the same message that the JSON file was very large, so I waited. I restarted after an hour when it seemed like nothing was happening. Second time, I tried it on a smaller folder, and it worked fine. I was using the Global/SpeciesNet model and had some results that didn’t make sense, so I selected those odd classifications for review. During the review, the program crashed, and I lost all my progress. I restarted and went ahead with the Post-Processing step and elected to separate the files into sub-directories for each classification hoping to be able to correct the mislabeled classifications after the fact. Is there a way to run through the Annotation step with the sub-directories since I can target those smaller folders?
I am running this on a government machine, but I was able to use the installer with admin privileges. This is version 6.14.
It looks like you guys might have stumbled upon a bug! You would help me solve it by reproducing the error in debug mode and sending me the output (or post it here, but it is quite a large piece of text and it is not very helpful for other users to read).