Closed jrenfree closed 1 year ago
@jrenfree, it's not clear to me that there is a task associated with this issue. I'm available today to explore this with you, if needed. I agree that it appears that at least one transect (121?) has an offshore tail that should be removed.
It was a minor comment on a separate task that you made after getting revisions back from Roger for the biomass report. I didn't want it to get buried in some random comment so I made a new task for it.
I reloaded Transect SD1055_109 in Echoview 13 on my local PC and it indeed appears that it is that diagonal line, so I think we should plan to exclude this transect from any analysis:
For Transect SD1059_121, it indeed appears that a section of the transit south on the western end was included. I reprocessed this line and ran it back through NASC(R), and put the results on the AST3 drive:
X:\SURVEYS\20210702_SAILDRONESummerCPS\PROCESSED\EV\CSV\SD1059\CPSFilter-13dB\POST-PROCESSED
Re-opening, as Transect 121 isn't plotting properly on the habitat map, so need to determine which portion of it is incorrect.
Transect 121 is now confirmed to be good, however:
Will work on correcting these.
Fixed Transect 117, and I believe the offshore portion of Transect 115 is missing because that's when SD1059 encountered hardware issues and had to come in. So I believe all should be fixed now, and latest files are on AST3.
Here is the most up-to-date habitat map:
I think I see these files on AST3, but I'm not readily finding the nasc_cps.csv versions. Have they been re-run through the R script or has the mask been applied otherwise?
For each Saildrone, the files you should use are in:
CPSFilter_-13dB\POST-PROCESSED
Thank you, I've updated my file set.
When plotting the Saildrone CSVs files, it appears that there are some odd-looking transects:
It appears that the southernmost odd transect is 109 from SD-1055. However, when I load the EV file for that transect, the GPS data does not appear correct, as it shows a gap in the data at that transect and interpolates that the ship goes over land:
If I then load the same GPS csv file in Matlab and plot that, the GPS data looks correct:
For now it appears to me that the process CSV files are fine, but for some reason Echoview is not correctly loading the GPS data at the moment. It does seems like transect 109 from SD-1055 is erroneous, and is likely a transit that got interpreted as a transect.
Will need to investigate more the partial transit on the western end of transect 121 conducted by SD-1059.