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

pick_main_stem changes order of tags, and does so differently for each census #215

Open
hmullerlandau opened this issue May 8, 2020 · 3 comments

Comments

@hmullerlandau
Copy link

pick_main_stem does not preserve the order of tags within a dataset, and it does not produce a consistent new order for different censuses. Thus, if pick_main_stem is applied to two different stem datasets of the same plot, the resulting "full" census datasets will have rows in different order by tag number. This generates problems if the resulting full data sets are then used with functions that assume rows are in the exact same order in different datasets, as for example assumed by all functions in the old CTFS R package. This means that, for example, calculating species-specific mortality rates using mortality.spp or for any other subset of the data will result in incorrect results. No error or warning messages are generated, however, so this problem could easily be overlooked. This problem was detected when applying pick_main_stem to the first two stem datasets for the Mpala plot.

@maurolepore
Copy link
Contributor

Thanks @hmullerlandau for reporting this bug. I'm not sure if anyone is now employed to maintain fgeo. If so, I hope they can follow up. If not, do you think one or a few people in the ForestGEO community would want to become maintaining this project?

@djj4tree
Copy link

This is a major issue and I was just coming here to open the issue. If this package is not being maintained, it should probably be removed from CRAN.

@DanielZuleta
Copy link

This is a major issue and I was just coming here to open the issue. If this package is not being maintained, it should probably be removed from CRAN.

Totally agree with Dan! I still receive emails asking questions about the tt_test function and just share the original code.

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

No branches or pull requests

4 participants