-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues running the example WASP14: pca problem #81
Comments
What does your config.yaml file look like? I had issues #76 trying the tutorial last month because the default config.yaml had changed (so the tutorial did not specify everything that needed changing). |
First I tried with the config file with two parameters and then with three parameters including metallicity, but with both the error was the same. In addition, the config file has the correct path. |
Hi @AngelicaJara , I'm sorry that the configuration file is not working properly for you. Could you paste the contents of your Given the Thank you. |
I just tried running the example case, and while I did not encounter the specific issue mentioned here, I did run into other issues. Given the general name of this thread, I'm going to mention those here, instead of opening a new thread. System configurations: Ubuntu 18.04.2, Python 3.7, and I installed Starfish from the git repo and using the same config file as suggested above. 1- 2- After I tweaked
Thanks, |
I've spent the last 8 months refactoring every part of Starfish, right now I am about 99% ready to merge my changes into master and push a release for Here is the documentation: https://starfish.readthedocs.io/en/develop/
|
Thanks for the quick response, I will try this one and update. |
Thanks again for your response. I managed to install and run the example case for a single order spectrum. I did not find the file used in that example anywhere (hd109085_sxd_xcleanspec_120203.fits), so I grabbed another spectrum from the IRTF library and it works beautifully. This new version is a great update to an already great package. :-) I think this issue can be closed when you release Just one last question: I don't see any documented way yet in thanks! |
Thank you for trying out the new version! Yes, that file is not in the repo because it is still proprietary to one of my collaborators and we need permission before hosting it online. I'm glad you got one of the archive stars to work, though. As for continuum-normalization, we don't currently offer that but it is possible that we could add a keyword (eg I personally haven't ever continuum normalized, though. @iancze can you weigh in? |
In my experience, continuum normalization is useful to take care of problems like bad/non-existent flux calibration and some slit problems. But none of these issues would be addressed efficiently by a Planck curve normalization I believe. One could do polynomials with considering outliers in the wavelength range of interest (which is the refuge to seek when dealing with IRAF/PyRAF for these problems). |
For the purposes of fitting a spectrum, continuum normalization is not necessary. The purpose of introducing the Chebyshev polynomials is to essentially fit for error in the flux calibration. Fitting continuum-normalized spectra directly without also allowing for small perturbations in the normalizing process (e.g., like with the Cheb polynomials) is tricky, since errors in the normalization process can bias your spectral fit. That said, if you already have continuum-normalized spectra (i.e., you don't have access the raw or flux-calibrated spectra), you can still use Starfish. The flux normalization term (Omega, or solid angle) and the calibration polynomials will still adjust to bring the model closer to the data, it's just that the value of these parameters won't have any physical meaning. |
I see, thanks! |
Hi! I installed Starfish in my laptop computer (Ubuntu 16.04). I followed the instructions and had no issues until trying to follow the example for WASP14.
The error appear when trying to run:
$ pca.py --create
$ File "pca.py", line 33, in
$ myHDF5 = HDF5Interface()
$ File "/home/angelica/Documentos/Starfish-master/Starfish/grid_tools.py", line 835, in init
$ self.grid_points = hdf5["pars"][:]
$ File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2840)
$ File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2798)
$ File "/home/angelica/.local/lib/python3.5/site-packages/h5py/_hl/group.py", line 169, in getitem
$ oid = h5o.open(self.id, self._e(name), lapl=self._lapl)
$ File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2840)
$ File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/tmp/pip-huypgcah-build/h5py/_objects.c:2798)
$ File "h5py/h5o.pyx", line 190, in h5py.h5o.open (/tmp/pip-huypgcah-build/h5py/h5o.c:3734)
$ KeyError: "Unable to open object (Object 'pars' doesn't exist)"
Apparently the parameter 'pars' is not defined. I looked in the code 'grid_tools.py' and everything seems to be in order. I have not modified anything in the 'grid_tools.py' code.
I do not know what's wrong, I'd appreciate checking my problem.
The text was updated successfully, but these errors were encountered: