Paths hardcoded in new preprocess scripts

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python, shell
Domain
documentation, tooling

Research direction

Start by inspecting the hardcoded paths in preprocess.new2.py and preprocess.new2.sh, then check the project documentation for setup and usage instructions. Determine whether the paths should be made portable or documented for users; done means the local setup is no longer assumed or the required paths are clearly explained.

Written by the indexing model from the issue text.

Description

I was trying to update my local install of preprocessing, and noticed that in the new scripts (preprocess.new2.py; preprocess.new2.sh) lots of paths are hardcoded to the local setup ("shares/CIBIO-Storage...") - this should be amended or clarified in the documentation for the wider user base if possible please.

Dominant language
Python
Stars
15
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SegataLab/preprocessing

All issues in SegataLab/preprocessing

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.