Kelle Cruz
Kelle Cruz
Update: we do indeed have a team Zenodo account.
This doesn't seem to be needed anymore.
Hi @ManonMarchand, thanks for reaching out! We aren't at the development phase yet of indexing tutorials hosted elsewhere, but it's still on the list. I believe the vision would be...
Yes, user should be warned but even better would be adding a `cache: True` option to the next version of checkout. In the meantime, the implementation provided by @nschloe worked...
There seems to be consensus that the Primary Header, e.g., whatever you'd put in HDU0, "should" be in `meta['header']`. There is not a consensus around what to do with extension...
Yes, you're right, I've changed my mind. I'm gonna edit my comment.
As a result of digging into this, I discovered that header data does not currently roundtrip using `Spectrum1D.write`. I propose that this be implemented using something like this: ``` #...
Summarizing relevant discussions from Slack: - _If someone modifies the spectrum, the keywords might become inaccurate._ My proposal is to add a warning that says something like, "Header keywords are...
We've tested the `spectrum.meta.update` method and it's pretty close! Problems include - extra END keywords. This makes many header keywords inaccessible by other tools. For example, ``` header=fits.getheader(tmpfile) ``` results...
- In my case, the COMMENT and HISTORY cards are stripped because they are `` - Even though I use `spec.meta.update(header)`, the meta doesn't roundtrip unless I use `update_header =...