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
I am trying to use your actel() package and directly import .csv files from my vemco/innovasea receivers, but the package is giving me an error message: "does not match to any of the supported hydrophone file formats!". Would you be able to provide an example .csv file from a vemco receiver that I could use as reference? Currently vemco/innovasea have updated their software from VUE to Fathom, so I am unsure whether this change in the exporting GUI has changed the formatting needed for your package. I attached two recent files that were exported when using Fathom.
This is indeed a relatively new format that actel doesn't yet know how to handle. I've reached out to other devs to see what's already out there to handle this. Might take a bit to move forward with this one but I'll update this as more info becomes available.
@hcg0509 it might be a while until there is a definitive solution for this (i.e. a solution where actel can smoothly, internally handle this detection format). To get going on this in the meantime (i.e. use another solution to then be able to feed these detections into actel using its standard format), I highly recommend attending the next OTN study hall (https://oceantrackingnetwork.org/study-hall/). All the people who can help with this are regularly there :) I'll make an effort to be there this week as well to continue this discussion.
I am trying to use your actel() package and directly import .csv files from my vemco/innovasea receivers, but the package is giving me an error message: "does not match to any of the supported hydrophone file formats!". Would you be able to provide an example .csv file from a vemco receiver that I could use as reference? Currently vemco/innovasea have updated their software from VUE to Fathom, so I am unsure whether this change in the exporting GUI has changed the formatting needed for your package. I attached two recent files that were exported when using Fathom.
VR2W-69 134254 2024-10-25 122531.csv
NexTrak-R1 801032 2024-10-25 093307.csv
The text was updated successfully, but these errors were encountered: