Closed brockho closed 7 years ago
Could it be that this only happens when multi-objective data are readin/processed?
The first issue also appears for single-objective data sets, for example, when running `cocopp.main('-o ppdata-I ALPS_hornby_noiseless.tgz ../../2010/rawdata/1plus1_brockhoff_noiseless.tar.gz').
The second problem seems to come from issue #1499, in other words, if I set cocopp.genericsettings.foreground_algorithm_list = []
in between two calls the above error is not produced anymore (but still does not show the correct index.html
file). Note that I have not tested with the latest code due to the bug introduced yesterday that crashed the postprocessing tests.
Last time, we discussed this issue, we realized that files are written directly to the ppdata
folder and not into a subfolder with the names of the algorithms when the data comes from different folders.
This issue is, as well, solved by the small change in e004a88.
As a follow-up of the discussion at #1507, I here report more details about the bug, I observed (happens in the current development branch):
The general issue is that postprocessing two algorithms from different folders causes quite a lot of unwanted behavior from the IPython shell:
cocopp.main('SMS-EMOA-SA.tgz ../../2016/coco-2.0-hvrefsets BestAfterWorkshop/GA-MULTIOBJ-NSGA-II/')
for example does not give any links in theindex.html
file and a subfolder with the comparison data is not produced. Instead, all plots are directly inppdata
. Note that the second algorithm has been already extracted by hand before the call, because the following does not work:cocopp.main('SMS-EMOA-SA.tgz ../../2016/coco-2.0-hvrefsets BestAfterWorkshop/SMS-EMOA-DE.tgz')
for example crashes with the following error:I can only imagine that both have to have something to do with the relative paths in the
cocopp.main
call. But it could also be related to too long paths as in #673, but I expected that at least a warning is issued in this case.