Skip to content

Enhancement request from Vincent #50

Description

@decarlof

So, here is my first impression.

  • The help of the command line is very hard to digest: after doing a copy / past of the full help in word, one ends up with 4 pages of command lines (without any line intervals). I feel like it has to be subdivided with the most important info at the top, or at least organize on the readthedoc webpage.

  • I feel like reading through the config file should be easier:

    • with most exotic functions at the very end (like beam hardening)
    • more comments explaining what is what (trying to put the comments on the same lines as the commands to minimize the length of the file)
  • Some info I was trying to get and did not find (I am not saying it is not there, but I did not find it within the time I spent looking at CLI):

    • doesn’t explain it can mixed config files and options
    • Doesn’t tell where data will be dumped. Personally, I don’t like the fact the recon are not in the same folder as the hdf files. I put experiment in one folder (PI name). If I switch to cli, hdf files should be transferred at the end of the scan into a sub-folder then rather than the GUP folder on txmtwo.
  • Remark: if data has problem (flat field not at the good location for instance), I usually reshape stacks inside my recon script. I can’t do it here but I think the best way is to apply the fix to the hdf5 directly. I should make a bunch of scripts ready for this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions