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

Need consistency of what files are called #173

Open
JohnHadish opened this issue Jul 10, 2020 · 2 comments
Open

Need consistency of what files are called #173

JohnHadish opened this issue Jul 10, 2020 · 2 comments

Comments

@JohnHadish
Copy link
Collaborator

The current nomenclature for what files are called is not consistent between the documentation and qkinc. This needs to be checked out, as it is confusing for even someone who is familiar with the program. I think there are too many file types that consist of some combination of c's , m's, and x's. It gets really confusing to try to tell them apart.

It is probably not realistic to change the names this late in the game, but I think we can help clarify by making everything really consistent. To start out, every file type should always be referenced by its full name and its extension. This should be both in qkinc drop downs:
image

and in documentation:
image

In addition, a single name needs to be decided on for `cluster composition matrix / cluster parameter matrix / cluster matrix' and it needs to be very consistent across all documentation.

Right now it feels like a treasure hunt every time I want to refer to one of these file types. I would prefer that they be renamed with moreunique names, but I recognize that may not be possible at this point. At the very least, we need consistency in what we are calling these different files, as there is very little right now.

@JohnHadish JohnHadish changed the title Need consistency of what files are called in qkinc Need consistency of what files are called Jul 10, 2020
@spficklin spficklin added this to the Release 3.4.3 milestone Jul 21, 2020
@spficklin
Copy link
Member

Agreed. This is an easy fix.

@bentsherman
Copy link
Member

These display names are defined in the data factory:

https://github.com/SystemsGenetics/KINC/blob/master/src/core/datafactory.cpp#L31

@JohnHadish I encourage you to submit a PR for this change since you only have to change the string values. No other code change is required.

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

3 participants