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

Write tests to ensure LongTable -> data.table -> LongTable is symmetric (i.e., doesn't lose data) #128

Open
ChristopherEeles opened this issue Oct 5, 2021 · 1 comment
Assignees

Comments

@ChristopherEeles
Copy link
Contributor

In manual testing I discovered that this symmetry is satisfied for the real NCI-ALMANAC LongTable object, but no the merckLongTable example data object.

Need to confirm that this is an issue with the example data object and not an issue with the coercion methods.

Also noticed that:

  • metadata needs to be added to data.table, or metadataMap has to set to empty in as(LongTable, 'data.table')
  • need to delete the longTableDataMapper attribute from a data.table during coercion back to LongTable or it ends up as an attribute of every data.table slot in the LongTable
@ChristopherEeles
Copy link
Contributor Author

Symmetry is true with MIT-MELANOMA.

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

1 participant