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

.rgdict and .seqdict files are not placed in the adam directory #945

Closed
jpdna opened this issue Feb 16, 2016 · 3 comments
Closed

.rgdict and .seqdict files are not placed in the adam directory #945

jpdna opened this issue Feb 16, 2016 · 3 comments

Comments

@jpdna
Copy link
Member

jpdna commented Feb 16, 2016

This may not be a bug, but I wanted to check that it is intentional that the .adam.rgdict and .adam.seqdict when creating .adam files with transform appear in the filesystem directory structure as siblings to the parquet .adam directory.
If these cannot go in the parquet .adam directory, could they at instead go into a .adam.dicts directory to keep the dir structure a little cleaner?

@heuermh
Copy link
Member

heuermh commented Feb 17, 2016

Note there are also .{name}.adam.rgdict.crc and .{name}.adam.seqdict.crc files.

@heuermh
Copy link
Member

heuermh commented Mar 22, 2016

The more I think about this, the more I think they should go in the .adam directory. I'm always bothered by other tools' handling of extra files (e.g. bowtie indices, picard sequence dictionaries, etc.), sometimes using command line arguments, sometimes using file base names, sometimes with certain file extensions, sometimes not.

Can we just hide these in the .adam directory and never have the user refer to them?

@heuermh
Copy link
Member

heuermh commented Mar 24, 2016

Bummer about all the linked dead commits, guess if you add fixes ... to the commit message, it stays on the linked issue page even if the commit has been rebased and force pushed out of existence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants