GNU Astronomy Utilities - Tasks: task #14300, Option management using new root...
You are not allowed to post comments on this tracker with your current authentication level.
task #14300: Option management using new root data structure.
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Wed 04 Jan 2017 03:19:03 PM UTC | ||
Should Start On: | Tue 03 Jan 2017 03:00:00 PM UTC | Should be Finished on: | Tue 03 Jan 2017 03:00:00 PM UTC |
Category: | All Gnuastro | Priority: | 5 - Normal |
Item Group: | Enhancement | Status: | Done |
Privacy: | Public | Percent Complete: | 100% |
Assigned to: | makhlaghi | Open/Closed: | Closed |
Effort: | 0.00 |
Mon 16 Jan 2017 03:22:25 AM UTC, comment #4: |
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
Sun 08 Jan 2017 02:05:27 AM UTC, comment #3: This was a very intriguing thought, and since I am going through the programs for using `gal_data_t', I thought it would be very useful if this system is adopted also, so the two jobs can be done in one round of learning/remembering how the programs work!
|
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
Wed 04 Jan 2017 11:58:22 PM UTC, comment #2: I just noticed that since we are using GNU C Library's Argp for parsing of arguments, we can use the each programs' argp_option array (and the `gal_commonargs_options' in `lib/commonargs.h' for the common options) to look up all the long option names automatically.
|
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
Wed 04 Jan 2017 03:38:59 PM UTC, comment #1: Building further on the suggested process, we can tell the library function how to interpret the values (for example keep the string value, or convert it to integer, or float) to the options with the `type' element of `gal_data_t' and define bit flags in its `status' element for further checks like a requirement that the value be larger than zero, or should be less than 1.
|
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
Wed 04 Jan 2017 03:19:03 PM UTC, original submission:
With the expansion of Gnuastro and its libraries (which will centralize many operations), the number of common options will increase. So it would be much more easier for the gnuastro users to set the values of common options only once for all of Gnuastro's programs (when they want to).
|
Mohammad Akhlaghi <makhlaghi>![]() ![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-01-16 | makhlaghi | Status | Postponed | ![]() |
Done |
Percent Complete | 10% | ![]() |
100% | ||
Assigned to | None | ![]() |
makhlaghi | ||
Open/Closed | Open | ![]() |
Closed | ||
2017-01-08 | makhlaghi | Percent Complete | 0% | ![]() |
10% |
2017-01-04 | makhlaghi | Summary | gnuastro.conf for common option, better .conf file/option management | ![]() |
Option management using new root data structure. |
This task has been completed and is now pushed onto my development fork. This was a major update and makes managing of the options and configuration files much more easier than before.
There are no longer any more macros, and there is only one instance of every option's short or long identifier string. New options can now be added very easily and more generally, it is much more easier to define new programs.
If you want to work on new programs/options, please pull this branch and base your work on this branch until it is merger with master, do not work on the master branch. Things are so much more clear and managable now :-)...