Closed brockho closed 7 years ago
There was no recent change related to this. I will check but it could be that we already have this behavior for a long time.
The data for this algorithm in the gforge data archive contains also tdat files. Where did you get your data?
But it's true, without the tdat files the post-processing stops.
This should be considered as a bug. The .tdat
files should not be necessary, as the maxevals-info can (and should) be taken from the .info
files, am I wrong? This relates to #1381
It turned out that the problem was a broken .extracted_...
folder. As soon as I deleted this one and run the postprocessing again, it worked.
However, the problem with missing `'tdat' files should be addressed - even if we don't provide those data files for the moment.
At the same time, we should consider a check while extracting the files that everything worked well (and to clean up if the extraction did not work well).
I opened two new issues #1445 and #1446 detailing the above two open things from my last comment. This issue can, thus, be closed.
I get a strange TypeError when postprocessing our
NEWUOA
data set with the latest version which I never got before:Did something related to this changed recently, @dtusar? I thought that
.tdat
files have been always optional so far and should stay that way, or am I wrong?