Analysing D-Foundations and/or D-Settlement with DFoundationsAnalysis and/or DSettlementAnalysis respectively gives a TypeError (Nonetype object is not iterable) when trying to get the results files out using .get_output_file().
Expected Behavior
Since the documentation says that an .err and/or .error.log file can be obtained. I expect to be able to get those files instead of getting a TypeError. When using the same input files in the software, I can see an error log and I would like to get that error log using this automatic analysis.
I’m not sure if I understand correctly, but it seems you’re running get_output_file(). In that case the extension defaults to get_output_file(extension='.sto', *, as_file=False), meaning you are trying to access the .sto file (which doesn’t exist).
Could you run get_output_file('.error.log'), to get the error log?
I get the TypeError than aswell. For what I can see, I think that when there is an error in the analysis no files are created, so when you try to take any output file it tries to iterate over None.
You’d need to monitor the job/worker while clicking the button, but I think your hunch is correct. One thing that could happen indeed is that there is no file created at all. If a d-series analysis runs and fails you’d get an error file, but if for example d-series tries to start but there is a license error or something else preventing the program to start altogether, you could end up with a situation in which you get no resulting file at all, full stop!
The best thing to do I think would be to see the actual log/job folder on the location of the worker while you trigger it from your app, is that feasible?