example command?

[ablwr]

Would be great to have an example command here -- the examples of the mandatory parameters are great but I am getting errors trying to do the one-liner necessary to kick off the project!

[retokromer]

I am not sure I understand the request. The parameters depend on the actual file structure and naming, and the current program does limit the choice very much.

[retokromer]

Regarding the optional parameters, more investigation is needed, but I will have the time only after the SEAPAVAA and FIAF conferences to delve into it myself, i.e. from end of April on.

[ablwr]

I am requesting an example of all the required parameters in use together as I keep getting errors when trying to run the program. I started then adjusting to try to get what is expected. Like, should it be -inputDir=‘/files’ or -inputDir /files or -inputDir =/files, etc etc? So I think it’d be helpful to have one line filled out as expected and successful for you.

…

On Apr 4, 2018, at 00:45, Reto Kromer ***@***.***> wrote: I am not sure I understand the request. The parameters depend on the actual file structure and naming, and the current program does limit the choice very much. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[retokromer]

Ah, sorry! It’s just (for the given example):

lenticular ~/TEST/SOURCE_FILES/ greyscale_ 0001 0057 NEW_FILES

I’ll add it as soon as I’m again on a normal WiFi. Thank you for the clarification!

[ablwr]

Ohhhh thanks! I’ll review and test soon when back at my computer :)

…

On Apr 4, 2018, at 07:30, Reto Kromer ***@***.***> wrote: Ah, sorry! It’s just lenticular ~/TEST/SOURCE_FILES/ greyscale_ 0001 0057 NEW_FILES I’ll add it as soon as I’m again on a normal WiFi. Thank you for the clarification! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ablwr]

Resolved in #3, thanks! Still at this moment getting a Abort trap: 6 on close but it seems to indeed be processing -- the rest surely continues to be "user error."