-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add command line options #6
Comments
Should a command line option approach as outlined above be used or a text file based input be used. The text file based input would be an excellent experimental ground to develop an interpreter module for the front end. Not sure if it would be all that conducive to quickly using the software. Command line options would probably be the fastest if one is familiar with the commands. I have also given thought to a GUI option. The inputs are so basic it would be fairly straight forward to offer a simple GUI interface to an actual user, not a developer user. |
I think a text file based input option should be used. Something like the following: title - name of run It's such a simple input file there is no reason to complicate it other than for fun. However I want something that works and then I can work on making it more user friendly (i.e. complicating it) |
The code to run multiple axle configurations and multiple span configurations is experimentally implemented in the dev_test file in the test directory. |
add argparse options:
blank: user defined spacing, axles, trailing load, and span lengths
-c --cooper: automatically adds cooper axles/loads
-al --alternate: automatically adds alt axles
-ar --aream: runs both cooper and alt
-bl --batch len: batch lengths
-ba --batch axle: batch axle configs
-h --help: display options and description each
The text was updated successfully, but these errors were encountered: