個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗Code repository to generate an automatically updated Fern Tree of Life.
Please see the accompanying paper:
All code is in R, and workflow is controlled with the targets package.
A docker image is available to run the code.
Docker tags match the version of FTOL; e.g., the image with tag 1.0.1 is the image used to generate FTOL v1.0.1.
Run the setup.R script to create the folder structure needed to store external files and download most of the data files automatically.
source("R/setup.R")
Alternatively, you can manually create the following folder hierarchy yourself:
_targets
└── user
├── data_raw
│ ├── ref_aln
│ └── restez
│ └── sql_db
├── intermediates
│ ├── blast_sanger
│ ├── iqtree
│ │ ├── plastome
│ │ ├── sanger
│ │ ├── sanger_1
│ │ ├── sanger_10
│ │ ├── sanger_2
│ │ ├── sanger_3
│ │ ├── sanger_4
│ │ ├── sanger_5
│ │ ├── sanger_6
│ │ ├── sanger_7
│ │ ├── sanger_8
│ │ ├── sanger_9
│ │ └── sanger_fast
│ ├── ref_seqs
│ └── treepl
│ ├── con
│ ├── ml
│ └── ts
└── results
Another folder called ftol_data (to store data files generated by this workflow that will be made available via the ftolr R package) also needs to be created in the project root. This folder is itself a repo that can be cloned from https://github.com/fernphy/ftol_data.
If setup.R was run successfully, it will have already downloaded and unzipped the input data files from FigShare.
Alternatively, you can do so manually following these instructions:
ref_aln.tar.gz (reference alignments) and restez_sql_db.tar.gz (local GenBank database) from FigShare (https://doi.org/10.6084/m9.figshare.19474316)ref_aln.tar.gz and put the ref_aln folder in _targets/user/data_raw/restez_sql_db.tar.gz and put the bat and sql_logs folders in _targets/user/data_raw/restez/sql_db.The script to generate the local GenBank database (restez_sql_db.tar.gz) is setup_gb.R.
The script (targets workflow) to generate the reference FASTA files for extracting target gene regions (ref_aln.tar.gz) is prep_ref_seqs_plan.R
The data that result from these scripts have been made available on FigShare as described above, so these generally shouldn't need to be run.
targets::tar_make().Note that this code was designed to be run on a multi-core machine, so the number of cores specified (e.g., here) may need to be changed.
The complete workflow takes 1-2 weeks to complete, with phylogenetic analysis taking up by far most of the time.
The container entrypoint accepts HOST_UID and HOST_GID environment
variables. When provided, it remaps the internal container user to your host
UID/GID before running any process. This ensures that files written to mounted
volumes (including git objects created by the targets pipeline) are owned by
your host user rather than root.
docker build -t joelnitta/ftol:latest .
run.sh runs the targets pipeline inside a container and exits when done:
bash run.sh
HOST_UID and HOST_GID are set automatically from the calling user.
A .devcontainer/devcontainer.json is provided for VS Code's Dev Containers workflow.
Create a .env file in the project root supplying your host UID and GID (check
with id -u and id -g):
UID=1001
GID=1001
Open the project in VS Code and run Dev Containers: Reopen in Container from the Command Palette. VS Code manages the container lifecycle and opens the project workspace automatically.
The container user owns /renv, so R packages can be installed directly
without root. To perform root-level operations (e.g. apt-get), open a
separate shell as root:
docker exec -u root -it <container_name> bash