resonATe issueshttps://gitlab.oceantrack.org/otndc/resonate/-/issues2020-09-09T17:13:07Zhttps://gitlab.oceantrack.org/otndc/resonate/-/issues/1metadata imports for resonATe2020-09-09T17:13:07ZJon Pyemetadata imports for resonATeWe should have functions in resonATe to import tag and deployment metadata from either sheets or the GeoServer / ERDDAP instance, and generalize them into dataframes that can be used by any functions in resonATe that need them.
The obv...We should have functions in resonATe to import tag and deployment metadata from either sheets or the GeoServer / ERDDAP instance, and generalize them into dataframes that can be used by any functions in resonATe that need them.
The obvious model here would be the ATT object in VTrack, where information about the animals and deployments are there when you need them but separated into dataframes. This object could then be depended on by internal and external functions and flows.
@ryangosse @bdeloRyan GosseRyan Gossehttps://gitlab.oceantrack.org/otndc/resonate/-/issues/2Expand Receiver Effiency Index analysis2023-08-02T14:49:50ZRyan GosseExpand Receiver Effiency Index analysisREI should be expanded to allow for more control over what's important. One technique is to weigh the stations with more species more heavily. There's might be more things we can add, but I need to get a paper from Jon firstREI should be expanded to allow for more control over what's important. One technique is to weigh the stations with more species more heavily. There's might be more things we can add, but I need to get a paper from Jon firsthttps://gitlab.oceantrack.org/otndc/resonate/-/issues/3Ingest for Frictionless Data2021-02-17T17:26:20ZRyan GosseIngest for Frictionless DataResonate should support reading in frictionless data.
[Sample Data](http://www.vliz.be/en/imis?dasid=5850&doiid=434)Resonate should support reading in frictionless data.
[Sample Data](http://www.vliz.be/en/imis?dasid=5850&doiid=434)https://gitlab.oceantrack.org/otndc/resonate/-/issues/4Create function for reading in deployment data for otn2021-05-07T18:30:36ZRyan GosseCreate function for reading in deployment data for otnCurrently all the deployment metadata prep is done in the REI function, we should extract that so it can be used by itself.Currently all the deployment metadata prep is done in the REI function, we should extract that so it can be used by itself.Ryan GosseRyan Gossehttps://gitlab.oceantrack.org/otndc/resonate/-/issues/5Keep extra columns when creating compressed detection events2023-07-12T11:55:41ZJon PyeKeep extra columns when creating compressed detection eventsCurrent compress_detections drops all non-standard columns and returns the event-by-event data, dropping most standard data columns as well. We could actually keep most of these columns if we either add them to the groupby in the case of...Current compress_detections drops all non-standard columns and returns the event-by-event data, dropping most standard data columns as well. We could actually keep most of these columns if we either add them to the groupby in the case of columns that shouldn't change within a detection_extract (collectioncode, institutioncode, etc), and additionally, we should provide a way for the user to keep all other non-standard columns. Giving them the choice of groupby.agg() methods (mean, first, etc) for all their extra columns, perhaps.Ryan GosseRyan Gossehttps://gitlab.oceantrack.org/otndc/resonate/-/issues/6Filtering behaviour2023-07-20T11:56:20ZJon PyeFiltering behaviourCurrently our filter functions return a list of dictionaries. User expected behaviour (and what our sister R program, glatos, is doing) is to have a column with a flag describing the filter results for each row of detection data. We shou...Currently our filter functions return a list of dictionaries. User expected behaviour (and what our sister R program, glatos, is doing) is to have a column with a flag describing the filter results for each row of detection data. We should return that format/style instead.Ryan GosseRyan Gossehttps://gitlab.oceantrack.org/otndc/resonate/-/issues/7Filters drop na station2023-07-11T14:44:12ZRyan GosseFilters drop na stationWhen you have NA stations in the detections file, the filters will drop them because pandas grouping does that by default. There's an option in pandas to not drop na groups so this should be v easyWhen you have NA stations in the detections file, the filters will drop them because pandas grouping does that by default. There's an option in pandas to not drop na groups so this should be v easyRyan GosseRyan Gosse