Git Product home page Git Product logo

protostars's People

Contributors

gully avatar

Watchers

 avatar  avatar

protostars's Issues

Figures for the paper

Possible Ideas:

  1. Teff and logg compared to theory and observations of Class I, II, and/or III young stars
  2. Spectrum with example composite model (optionally extinction curves, etc)
  3. Distribution of inferred solid angle ratio
  4. Distribution of r_K
  5. Corner plot for a subset of other interesting parameters?
  6. Visualization of priors over the posteriors?
  7. Constraints from independent information-- photometry, etc.

Restructure star.py scripts to be housed in individual project code/ repos

The Starfish star.py code would be renamed to star_{*project*}.py

So for example we would have:

$protostars/code/star_protostars.py --samples=5000 

instead of having a whole bunch of star_{misc_descriptor}.py (e.g. star_BB.py ) all living in the $Starfish/scripts/ directory.

There are tradeoffs to both approaches, but I think this revised strategy is closer to the customized work I am doing for multiple different projects.

The Right Thing To Do is to rewrite Starfish with a base model class from which I can inherit and extend functionality, but in practice many of these experiments are one-offs right now, and so good design is probably not urgent. Eventually the experience and insight I gain from these experiments will give me a clearer vision on how to do this right.

Implementation with Av and scattering

Should we implement an Av?
I'm of two minds about this.

Some tradeoff considerations:

  1. The Av value will not be significant because the emergent spectrum comes from scattered light, which introduces a non-standard spectral shape, hampering accurate retrieval of Av anyways.
  2. More evolved stellar systems will not suffer from this problem as much, so we might as well implement it anyways.
  3. We can use the Av value it gives us to demonstrate that it's unphysical and therefore verify the extent to which scattered light is playing a role.
  4. Of course we don't really know the overall spectral shape or if the models are accurate in the absence of scattering and extinction anyways, so there's really no point right now to use Av and not just let the Chebyshev polynomials pick up the slack.

Simulated JWST data of S68N

It'd be really neat to show a comparison of what we can do now with Keck, and what JWST will be able to do. This should be considered a bonus since it's basically fake (ie synthetic) data, but could be neat.

Do a Starfish job with relaxed priors on black body temperature (not merely T_BB = 1100)

This exercise will result in highly degenerate posteriors of solid angle, etc.

Interestingly, we might be able to put a prior on the solid angle ratio-- the disk should be larger than the Star! Of course geometrical considerations could limit the strength of the prior we can assign-- a thin ring of disk inner wall could be consistent with an apparent area less than the (proto)stellar surface area.

Bugfix-- Why does raw_models metadata blobs fail?

Traceback (most recent call last):
  File "/Users/gully/GitHub/protostars//code/star_protostars_Av.py", line 216, in <module>
    np.save('temp_raw_models.npy',sampler.blobs)
  File "//anaconda/envs/Starfish/lib/python3.5/site-packages/numpy/lib/npyio.py", line 491, in save
    pickle_kwargs=pickle_kwargs)
  File "//anaconda/envs/Starfish/lib/python3.5/site-packages/numpy/lib/format.py", line 573, in write_array
    pickle.dump(array, fp, protocol=2, **pickle_kwargs)
OSError: [Errno 22] Invalid argument

Verify the solid angle ratio is calculated correctly for star and disk

Right now star_BB.py computes the relative flux ratio of the star to disk like so:

F_bol1 = self.F_bol_interp.interp(p.grid)
F_bol2 = stef_boltz * p.T_BB**4.0 ## Radiance from black body
self.qq = F_bol2/F_bol1[0]

and then computes the net model like so:

model1 = self.Omega * (self.chebyshevSpectrum.k * self.flux_mean + X.dot(self.mus))
# Black body
model2 = self.Omega2 * self.qq * self.BB_lam.value * self.chebyshevSpectrum.k

# Return a "metadata blob" of both spectrum models
raw_models = [model1, model2]

net_model = model1 + model2

The absolute values of the solid angles have no meaning since we do not have absolutely flux-calibrated spectra. However the relative value of the solid angles is physically meaningful. How much bigger is the disk than the star (since they share the same distance).

However, the posterior values I'm getting for logOmega2 are much less than those for logOmega, suggesting that something is wrong in the co-factors I'm assuming for the relative flux ratio of the Phoenix models and Black Body.

TODO's:

  • Assess the units of Phoenix and astropy's Black Body.
  • Revisit the F_bol assumptions

Text updates

  • What is the wavelength range of the NIRSPEC-7 filter? Website says 1.84 - 2.63, but the short wavelength portion is inaccessible. Telluric atmosphere is present here.

Exploratory data analysis

  • Explore metadata from Keck Archive
  • Examine the spectrum of S68N
  • Calculate and verify the spectral resolution and sampling
  • Save ascii spectrum to `HDF5 for Starfish

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.