Closed jessicas09 closed 1 year ago
Hi Jessica!
Thanks for trying out actel.
I can see from your spatial.csv file that you have listed WB6, 7, ..., 13 as "Hydrophone" stations, rather than "Release" stations. Is that intentional? I.e. do you have hydrophones at those locations? If, for example, WB6 is both the location of an hydrophone and also a location where fish were released, then you should create two stations (one for the hydrophone and another for the release).
e.g.:
Station.name | Latitude | Longitude | Section | Array | Type |
---|---|---|---|---|---|
WB6 | ... | ... | Bay | WB6 | Hydrophone |
WB6-R | ... | ... | WB6 | Release |
Then use "WB6-R" as the release site for your fish.
Hope that helps!
Yes, WB6, 7, ..., 13 are all hydrophones. And the other ones (WB210915-03...WB220926-13) are individual fish IDs. I have the "Release" arrays as the location where the fish would first be expected to cross (aka the closest hydrophone when released). So I think that's the same as your example, right? Except I'm using the fish ID as the release site name. Does that not make sense?
The "Release.site" in the biometrics needs to match the name of a "Release" station in the spatial file, that is what is causing the error.
There are two ways you can fix this:
1) If the specific release coordinates are not extremely important for the speed at release, I would group the "release" stations that have the same expected first array into a single station and use that one as the release site for the respective animals.
2) If the specific release coordinates are important, then adjust the "Release.site" in the biometrics to match the corresponding release station in the spatial (i.e. the shark ID essentially becomes the release site for the current situation).
AH! I thought that the "release site" on the biometrics needed to match one of the "hydrophone" Station.name's on the spatial, in order to indicate which hydrophone the animal would first appear on.
This worked! Thanks for your (quick!!) response and explanation!! You rock!
I'm receiving the following error and I'm not sure why. I've already confirmed that the release sites are spelled exactly the same (including no extra spaces) on both files. Has anyone else had this issue?