Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement infrastructure for simple loci library installation and usage #43

Closed
dbolotin opened this issue Oct 23, 2015 · 0 comments
Closed

Comments

@dbolotin
Copy link
Member

This issue is connected to #42

User story 1 (installation of loci library)

  1. If I have a custom loci library and want to use it without specifying the full path I can put it into following locations:
    • PATH_TO_MIXCR_SCRIPT/reference/ for system-wide installation
    • ~/.mixcr/reference/ for user-local installation
    • working directory . or ./reference
  2. Symlinks in any of the following cases should be correctly dereferenced by MIXCR

User story 2 (usage of custom loci library)

  1. If I have a custom loci library I can use it, either I have installed it or not, in the following way:
    • If it is installed as described above:

      mixcr align --lociLibrary myLL ....
      mixcr assemble ...
      mixcr exportClones ...
      

      I don't have to specify loci library second time in assemble, as *.vdjca file already contains this informatio

    • If I just have a file somewhere in the file system:

      mixcr align --lociLibrary /path/to/myLL ....
      mixcr assemble  --lociLibrary /path/to/myLL ...
      mixcr exportClones  --lociLibrary /path/to/myLL ...
      

User story 2 (default loci library)

  1. Any installed libraries with names other than default.ll will be used only if user specified it on the align step, the internal mi.ll will be used if --lociLibrary option is not used.
  2. Library installed with the name default.ll will be used by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant