Giter Site home page Giter Site logo

igmspec's Introduction

igmspec

Welcome to the igmspec repository. The igmspec database is intended to provide all publicly available spectra that probe the intergalactic medium (IGM). Parties interested in accessing and interfacing with the database should see the primary publication: http://coming_to_arxiv.soon Further documentation is available at readthedocs: http://specdb.readthedocs.io/en/latest/igmspec.html

This repository has two main purposes:

  1. Provide additional descriptions of the datasets ingested into the igmspec database.

  2. Maintain the software required to build the database.

It is rather unlikely that you will want or need to clone this repository.

igmspec's People

Contributors

astronomeara avatar jhennawi avatar profxj avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

igmspec's Issues

Other Surveys

Please add to this list:

  • HST STIS/GHRS from Cooksey+10
  • HST COS-Halos, COS-Dwarfs
  • Gabor's HeII survey
  • MagE LLS survey (Fumagalli+ 15); overlaps with HD-LLS
  • H100 (Neeleman+13)
  • ESI DLAs (Rafelski)
  • GRBs galore
  • QPQ (eventually)
  • HIRES dataset from UCSD (Pro+07)

Version 2

This thread should capture the wish list for v02.

v02 incorporate new datasets, continua and software
to generate proprietary datasets.

v02 will also include a paper to be submitted (or at least posted).

Splicing

Add a splice option for multiple spectra

Headers

Consider including the FITS headers for all non-SDSS/BOSS data.

And even those too..

Version history

Should the code be written to:
a. Enable the "exact" reproduction of every version release of the DB?
b. Build on pervious versions or start over building from scratch?

XQ-100 records have wrong IGM_ID

@profxj

In the v02 database, XQ-100 quasars are given wrong (and duplicated) IDs. They span row 382443 to row 382539, but their IDs are from 1 to 97.

And hence after the XQ-100 quasars, the row number of a record is not the same as its IGM_ID. For example row 382540 has IGM_ID 382443.

Would like to get an amended copy of the database even before v03 release.

Name game

Let's decide on the name for this repository/package

JMO: sigma = Spectra of the IGM for Astrophysics

Fix GGG DATE-OBS

SMJD is for SDSS

For GMOS either refer to the FITS header of the spectrum or the paper.
Several targets got reobserved, so the FITS header is not always very informative.

z BOSS

Should we use Z_PCA or Z_PIPE or ??

Survey_ID

Make these unique identifiers for the quasars, not the spectra.
GGG, at the least, needs fixing

Multi-slit data?

Suppose, as eventually in the case of HS1700 for example, we have a set of multi-slit data from MOSFIRE, LRIS, DEIMOS, etc near a quasar from our surveys. Should we incorporate those spectra into igmspec? It could facilitate fast searches for galaxies near certain redshifts in the qso spectrum. May be too much work for too specific a return.

v03

Add at least the following:

  • BOSS DR14
  • KODIAQ DR2
  • Eilers' QSOs
  • First set of GRB spectra

"proprietary" version

Any interest in making a proprietary version of the DB so that we can include "in-work" data (e.g. WFC3 pairs, operation headshot, etc) spectra. perhaps a call to get_igmspec that requires a password (not sure how one would do that....)

Installation problem

When trying to reinstall specdb from scratch (using python setup.py install), I now get the following error:
(astroconda) ntejos@arrakis:~/python/specdb$ python setup.py install
running install
running bdist_egg
running egg_info
writing specdb.egg-info/PKG-INFO
writing top-level names to specdb.egg-info/top_level.txt
writing dependency_links to specdb.egg-info/dependency_links.txt
reading manifest file 'specdb.egg-info/SOURCES.txt'
writing manifest file 'specdb.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
copying specdb.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying specdb.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying specdb.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying specdb.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
creating 'dist/specdb-0.1.dev0-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
Traceback (most recent call last):
File "setup.py", line 86, in
setup(**setup_keywords)
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/setuptools/command/install.py", line 67, in run
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/setuptools/command/install.py", line 109, in do_egg_install
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/distutils/cmd.py", line 326, in run_command
self.distribution.run_command(command)
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/setuptools/command/bdist_egg.py", line 223, in run
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/setuptools/command/bdist_egg.py", line 467, in make_zipfile
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/site-packages/setuptools-27.2.0-py2.7.egg/setuptools/command/bdist_egg.py", line 460, in visit
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/zipfile.py", line 1151, in write
self._writecheck(zinfo)
File "/home/ntejos/anaconda/envs/astroconda/lib/python2.7/zipfile.py", line 1117, in _writecheck
" would require ZIP64 extensions")
zipfile.LargeZipFile: Filesize would require ZIP64 extensions

Not sure if it's caused by specdb or something else...

Simple Usage example

Hi all,
I think there is a missing line in the Simple_Usage.ipynb:

I added this to the initial inputs:
from astropy import units as u

Also, when I grab the example spectra there is "sig" keyword missing.
I guess the sigma spectrum is missing?

I ran the cell:

Grab spectra

J0812spec, meta = igmsp.grab_spec('KODIAQ_DR1', ids0812)

and got this in return:
Staged 1 spectra totalling 0.0032 Gb

Loaded spectra

TypeError Traceback (most recent call last)
in ()
1 # Grab spectra
----> 2 J0812spec, meta = igmsp.grab_spec('KODIAQ_DR1', ids0812)

/anaconda/anaconda/envs/astroconda/lib/python2.7/site-packages/igmspec-0.0.dev0-py2.7.egg/igmspec/interface_db.pyc in grab_spec(self, survey, IGM_IDs, verbose, **kwargs)
195 return
196 # Generate XSpectrum1D
--> 197 spec = XSpectrum1D(data['wave'], data['flux'], sig=data['sig'], masking='edges')
198 # Return
199 return spec, self.meta

TypeError: init() got an unexpected keyword argument 'sig'

Nino

Cannot build the database using get_igmspec

The error is

(astroconda)ntejos@arrakis:~/python/igmspec/DB$ get_igmspec 
Traceback (most recent call last):
  File "/home/ntejos/anaconda/envs/astroconda/bin/get_igmspec", line 6, in <module>
    exec(compile(open(__file__).read(), __file__, 'exec'))
  File "/home/ntejos/python/igmspec/bin/get_igmspec", line 12, in <module>
    import igmspec.scripts.get_igmspec as get_igmspec
ImportError: No module named get_igmspec

Seems some sort of compatibility issue w/r to the old igmspec implementation.

Continuua

Consider adding continua, e.g.
SDSS-DR7 (mine or Gunagtung's)
BOSS (QPQ)
GGG (from LLS analysis?)

Clean vstack

Add a check before writing that all meta tables
can be stacked using specdb.utils.clean_vstack

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.