Closed hayalaso closed 3 years ago
Yes, I see how that might be a problem.
I have two ideas how this could be done instead:
roifile
property, not the roimap
one, and make sure that HAL reads the actual ROI map from the ROI file when e.g. a model map hd5 file with a map ROI is read in. Probably less work but dangerous because
a. The roifile
is not always guaranteed to still exist (e.g. if a file is copied to a different file system)
b. It's currently not mandated that the roifile
exists at all, users are free to use a healpix map in memory when setting up the ROI.Thoughts?
I was actually starting to look into something like point 2, to save the ROI map in the hd5 file.
I see from here, that the dictionary with the ROI information is created. Is the roimap
necessary to be here for other functions? Otherwise, I was thinking of adding a try/exception
in the class method from_dict
of HealpixMapROI
when trying to read a hdf5 file.
Fixed by #56
I'm trying to save the residual and model maps of my analysis. I wasn't able due to the following error
It looks like the header of the ROI object is too large.
I did a quick test, using HealpixConeROI, and my program was able to run fine.
I printed the information of the ROI. When using the Healpix Map one:
and when using Healpix Cone:
It looks like the header is trying to save the roimap, which might cause the problem?