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 a "version" command #180

Open
JohnHadish opened this issue Apr 1, 2021 · 1 comment
Open

Need a "version" command #180

JohnHadish opened this issue Apr 1, 2021 · 1 comment

Comments

@JohnHadish
Copy link
Collaborator

JohnHadish commented Apr 1, 2021

In addition to it's current commands (run,chunkrun,merge,dump,inject, and settings) KINC should have a command called version that simply says which version of kinc is being run. This is important, as it appears that different versions of kinc open files differently. It would be nice to have an easy command to identify which version is being run.

The following two images are the same file made with KINC 3.4.2, but opened with two seperate qkinc versions:

Opened using qkinc packaged with 3.4.2:
image

Same file opened using qkinc packaged with 3.4.1:
image

@JohnHadish
Copy link
Collaborator Author

JohnHadish commented Apr 1, 2021

Or even better, just add a line to the top of the output you get when you run the commands kinc and kinc help:
(First line of output is suggested addition)

[john.hadish@login-p1n01 GEMmaker_211]$ kinc
**kinc version X.X.X**

Help: kinc help <command>

Get help about the specific command <command>.

Valid commands:

     run: Run an analytic in normal mode. MPI is automatically detected. If no
          MPI is detected then the analytic will run in single mode.

chunkrun: Run an analytic in chunk run mode. This mode will execute the
          analytic on a subset of the data and save its results in a temporary
          file.

   merge: Merge all temporary result files from chunkruns into the finished
          output data objects of the analytic run.

    dump: Dump the system or user metadata of a data object to standard output
          as JSON formatted text.

  inject: Inject new user metadata into a data object from a JSON formatted text
          file, overwriting any user metadata the data object currently
          contains.

settings: Access the global persistent settings for this program to either view
          those settings or change them.

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