Mercurial > repos > oinizan > frogs
diff test-data/databases/frogs_picrust2_functions.loc @ 27:646bee69560f draft
planemo upload for repository https://github.com/geraldinepascal/FROGS-wrappers/ commit b6afc353bed8654c3a9ca56d194ecc7827d9ca18
| author | oinizan |
|---|---|
| date | Wed, 30 Apr 2025 06:13:02 +0000 |
| parents | dfaf556d2a20 |
| children |
line wrap: on
line diff
--- a/test-data/databases/frogs_picrust2_functions.loc Thu Apr 03 05:58:59 2025 +0000 +++ b/test-data/databases/frogs_picrust2_functions.loc Wed Apr 30 06:13:02 2025 +0000 @@ -18,16 +18,22 @@ #the copy number of gene families present in the predicted genome for OTU, # given a tree and a set of known trait values (FROGS_frogsfunc_placeseqs). # -#PICRUSt2 files are present in the arborescence of PICRUSt2. Please consult -#PICRUSt2 documentation to find out where they are located in your environment. +#PICRUSt2 files are present in the arborescence of PICRUSt2. +# +#<value_as_marker_gene> <name_as_fun_db> <fun_db_or_path_to_marker_copy_numbers> <fun_db_or_path_to_fun_copy_numbers> <version> + +# For 16S data (see the 6 first lines), PICRUSt2 only takes the db name of the database as input (for exemple EC). +# With ITS and 18S data, you have to specify the path of marker gene counts files. +# # -#If you are not comfortable with picrust2 command lines, just create .loc files -#with EXAMPLE FOR TEST files remembering to replace <PATH_TO> with the real path. +# Bellow you will find out how to implement this loc file. # -#<marker_gene> <db> <picrust2_input_marker> <picrust2_input_function> <picrust_version> +# The indicated path is the one if you do not change the default galaxy config of conda directory. +# Just adapt path by replacing <Galaxy_dir> with the real path and eventually the picrust version. # -#With 16S data, PICRUSt2 only takes the dname of the database as input (for exemple EC). -#With ITS and 18S data, you have to specify the path of marke gene counts files. +# If you are not using this default conda behavior, please consult PICRUSt2 documentation to find out where they are located in your environment. +# +# # # EXAMPLE FOR TEST : 16S EC EC EC 2.5.1
