You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The read_phyloseq, read_biom2phyloseq etc useq datasets from QIITA and DynamicsIBD. We had to remove these data sets from the package due to Bioc constraints for package size (4Mb). I have commented out the respective parts in the documentation (Rd files as well as docs/Rmd files) but these need to be updated. One solution is to make a separate example data repository online together with the tutorial. The larger data sets can then be fetched from there on-the-fly, This will require access to internet connection however.
The text was updated successfully, but these errors were encountered:
@binmat has just prepared phyloseq data packages for David and Ravel data sets, and in microbiome pkg we have phyloseq objects for three studies. More likely to come. In my view, the best way would be to be to follow standard practices and prepare either data objects that can be loaded with data(..) command; or entire data packages. But for examples & tutorials we also need other formats (such as biom), therefore an example data repository should be useful. If you agree, we could move microbiomedatarepo under microbiome organization in Guthub (perhaps the repository name can then be shortened to just data?) until a better solution emerges? You have now full rights, I had not noticed this.
The read_phyloseq, read_biom2phyloseq etc useq datasets from QIITA and DynamicsIBD. We had to remove these data sets from the package due to Bioc constraints for package size (4Mb). I have commented out the respective parts in the documentation (Rd files as well as docs/Rmd files) but these need to be updated. One solution is to make a separate example data repository online together with the tutorial. The larger data sets can then be fetched from there on-the-fly, This will require access to internet connection however.
The text was updated successfully, but these errors were encountered: