Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible issues with bringing sapfluxnetQC1 up to date #47

Open
7 tasks done
MalditoBarbudo opened this issue Sep 17, 2024 · 10 comments
Open
7 tasks done

Possible issues with bringing sapfluxnetQC1 up to date #47

MalditoBarbudo opened this issue Sep 17, 2024 · 10 comments
Assignees

Comments

@MalditoBarbudo
Copy link
Member

MalditoBarbudo commented Sep 17, 2024

  • Spatial packages: sapfluxnetQC1 is based in sp, rgdal and rgeos when using spatial objects (coordinate checks...). This will likely fail in a recent R installation. rgeos is also retired.
  • GSODRdata package used to get wordclim values at the nearest stations has been retired. We need a new way to obtain these values to calculate the site biome.
  • tpl package for fixing species names is also unmaintaned, we need to implement an alternative
  • methods for SfnData class must be fixed, as some of them fail (i.e. [). Or, just implement the class in sapfluxnetr here, if trivial.
  • Fix failing tests
    • deprecation notices
    • others
@rafapoyatos
Copy link

For the taxonomy, check the packages I mention in issue #46

@MalditoBarbudo
Copy link
Member Author

Deprecated packages (sp, rgeos...) fixed.
Methods for SfnData class fixed.

A lot of tests failing, due to different reasons (tests based in removed packages and output, tests issuing unexpected warnings due to deprecation notices, tests failing for changed behaviours in dependencies). Working on it.

MalditoBarbudo added a commit that referenced this issue Sep 19, 2024
@MalditoBarbudo
Copy link
Member Author

All tests passing :)

@vflo
Copy link

vflo commented Sep 25, 2024

All the QC1 and QC2 works fine with ESP_VAL_SOR test dataset.

@vflo
Copy link

vflo commented Sep 26, 2024

I've included a check to determine if the coordinates are on land. However, @MalditoBarbudo, I'm not sure how to include a test process.

@vflo
Copy link

vflo commented Sep 26, 2024

test: 'wrong coordinates are plotted correctly' doesn't work properly. I'm not saving the coordinates plots now, just printed in the report.

@MalditoBarbudo
Copy link
Member Author

I've included a check to determine if the coordinates are on land. However, @MalditoBarbudo, I'm not sure how to include a test process.

I've been looking at the changes, and after all the process, new messages are shown when the plot is located in water. In the
tests for coordinates, in B2 is where I tested the is inside country trait. Basically I created bad coordinates and good coordinates and expect the correct messages. In this case I would add a set of coordinates that simulate the on_water trait and check for the presence of the correct message, as well as the correct number of bad coordinate sites.

@MalditoBarbudo
Copy link
Member Author

test: 'wrong coordinates are plotted correctly' doesn't work properly. I'm not saving the coordinates plots now, just printed in the report.

Not sure what is happening here, but changes were made to the plot code as well as forcing the plot argument. Could be worth to check the code there.

@rafapoyatos
Copy link

I successfully used the 'devel' QC1 with GBR_DEV_* datasets! @vflo
Just one comment on the species checks @MalditoBarbudo . What happens when a contributor only defines taxa at genus or even family levels? Can we detect this and use some common terminology: e.g. 'Quercus sp.' when somebody reports only 'Quercus' or 'Quercus spp.' (incorrectly). What about family-level? Could we use e.g. 'Myrtaceae fam.'? See here , for example.

@MalditoBarbudo
Copy link
Member Author

@rafapoyatos
Not sure what happense in that case. I'll need to revisit the species checks to see if is possible or already done by one of the dependencies used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants