Attract init
You are about to submit a new Pull Request. Before continuing make sure you read the contributing guidelines.
Checklist
- [ ] Tests added for the new code
- [ ] Documentation added for the code changes
- [x] Does not break licensing
- [ ] Does not add any dependencies, if it does please add a thorough explanation
Summary of the Pull Request
Here I have
- ATTRACT installation guide
src/haddock/modules/sampling/attract/install.md - A beginning of an [attract], that currently:
- checks ATTRACT installation and env variables
- converts protein and RNA into ATTRACT coarse-grained
- splits RNA into fragments
- prepares folder for the docking
- passes unchanged all-atom protein & RNA to the next module
Related Issue
#1034
Additional Info
On tintin you can use:
export ATTRACTDIR=/trinity/login/arha/tools/attract/bin
export ATTRACTTOOLS=/trinity/login/arha/tools/attract/tools
export LD_LIBRARY_PATH=$ATTRACTDIR:$LD_LIBRARY_PATH
export LIBRARY=/trinity/login/arha/tools/nalib
export RANDSEARCH=/trinity/login/arha/data/ssRNA/randsearch
instead of installing ATTRACT from scratch
What about creating a Docker/Singularity container instead with everything inside ? I am thinking here of a solution for the web app.
What about creating a Docker/Singularity container instead with everything inside ? I am thinking here of a solution for the web app.
Not really an option for this case, the third-party software has a hard dependency on py2 while this project is py3. Making a container in which both can co-exist will a bit complex. Makes more sense to containerize the older code and build a wrapper for it.
For attract specifically the maintainer has published an image @ rbps/attract (mobyle2.rpbs.univ-paris-diderot.fr something repository) which can be seamlessly integrated into the web interface as well - it's all the same technology :)
@rvhonorato, can you add here the docker-related script(s) you made, please? And that 1-line call that allows to run /path/attract/tools/reduce.py. Thank you!
un-assigning myself since it seems like this will not go down the containerization route
I would like to continue to work on it, switching from raw ATTRACT code to docker container. Thus let’s keep this branch, even tho it’s pretty old.
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This PR was closed because it has been stalled for 5 days with no activity.