All numerical analysis programs must provide results in a form the analyst can present in papers and presentations, to client, etc. From my experience using DDA, the faster the results can be post-processed, the more analysis I can perform per unit time.
Excel is an obvious post-processing programming for users on MS Windows systems. However, I don't use Excel, prefering to write to text files and post processing with unix tools specialized for this purpose (awk, sed, grep, perl etc.).
For the purposes of future development, what output formats for results would you, the analyst, prefer to use? Excel? Matlab? MySQL? Would you be willing to pay for implementing such support? Would you be willing to implement that support and contribute such code to the DDA project here at sourceforge.net?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CSV files seem to be the way to go for tabular output data. This ensures that people who use Excel can easily open the files, as well as providing those of us using scripting languages like Python something easy to work with.
One of the major issues I have with UDEC is the terrible output format of the HIST files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It wouldn't be that hard to have DDA emit the
data and simple postprocessing commands
directly in the Python language. Such could be
written as a DLL and loaded at runtime.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All numerical analysis programs must provide results in a form the analyst can present in papers and presentations, to client, etc. From my experience using DDA, the faster the results can be post-processed, the more analysis I can perform per unit time.
Excel is an obvious post-processing programming for users on MS Windows systems. However, I don't use Excel, prefering to write to text files and post processing with unix tools specialized for this purpose (awk, sed, grep, perl etc.).
For the purposes of future development, what output formats for results would you, the analyst, prefer to use? Excel? Matlab? MySQL? Would you be willing to pay for implementing such support? Would you be willing to implement that support and contribute such code to the DDA project here at sourceforge.net?
CSV files seem to be the way to go for tabular output data. This ensures that people who use Excel can easily open the files, as well as providing those of us using scripting languages like Python something easy to work with.
One of the major issues I have with UDEC is the terrible output format of the HIST files.
It wouldn't be that hard to have DDA emit the
data and simple postprocessing commands
directly in the Python language. Such could be
written as a DLL and loaded at runtime.
What are the problems with the HIST files? Would you mind copying a snippet from some output to
use as an example, then adding comments to that?