stardis

TARDIS stellar radiative transfer

https://github.com/tardis-sn/stardis

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.0%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

TARDIS stellar radiative transfer

Basic Info
Statistics
  • Stars: 16
  • Watchers: 12
  • Forks: 18
  • Open Issues: 27
  • Releases: 6
Created over 4 years ago · Last pushed 11 months ago
Metadata Files
Readme Contributing License Zenodo

README.rst

STARDIS Stellar Radiative transfer
----------------------------------

Welcome to STARDIS!
STARDIS is an LTE radiative transfer Python package that utilizes the TARDIS infrastructure 
to generate synthetic stellar spectra. For more information about STARDIS, 
including a quickstart notebook, physics walkthrough and installation instructions, go to our `documentation page `_. 
Or, try running the `quickstart notebook `_ yourself!

To learn more about TARDIS, including documentation and collaborator information, go `here `_.

License
-------

This project is Copyright (c) TARDIS Collaboration and licensed under
the terms of the BSD 3-Clause license. This package is based upon
the `Openastronomy packaging guide `_
which is licensed under the BSD 3-clause licence. See the licenses folder for
more information.


Contributing
------------

We love contributions! stardis is open source,
built on open source, and we'd love to have you hang out in our community.

**Imposter syndrome disclaimer**: We want your help. No, really.

There may be a little voice inside your head that is telling you that you're not
ready to be an open source contributor; that your skills aren't nearly good
enough to contribute. What could you possibly offer a project like this one?

We assure you - the little voice in your head is wrong. If you can write code at
all, you can contribute code to open source. Contributing to open source
projects is a fantastic way to advance one's coding skills. Writing perfect code
isn't the measure of a good developer (that would disqualify all of us!); it's
trying to create something, making mistakes, and learning from those
mistakes. That's how we all improve, and we are happy to help others learn.

Being an open source contributor doesn't just mean writing code, either. You can
help out by writing documentation, tests, or even giving feedback about the
project (and yes - that includes giving feedback about the contribution
process). Some of these contributions may be the most valuable to the project as
a whole, because you're coming to the project with fresh eyes, so you can see
the errors and assumptions that seasoned contributors have glossed over.

Note: This disclaimer was originally written by
`Adrienne Lowe `_ for a
`PyCon talk `_, and was adapted by
stardis based on its use in the README file for the
`MetPy project `_.

Owner

  • Name: TARDIS RT collaboration
  • Login: tardis-sn
  • Kind: organization
  • Email: tardis.supernova.code@gmail.com

Radiative Transfer code for supernovae

GitHub Events

Total
  • Create event: 4
  • Release event: 4
  • Issues event: 21
  • Watch event: 5
  • Member event: 2
  • Issue comment event: 46
  • Push event: 67
  • Pull request review comment event: 55
  • Pull request event: 70
  • Pull request review event: 96
  • Fork event: 2
Last Year
  • Create event: 4
  • Release event: 4
  • Issues event: 21
  • Watch event: 5
  • Member event: 2
  • Issue comment event: 46
  • Push event: 67
  • Pull request review comment event: 55
  • Pull request event: 70
  • Pull request review event: 96
  • Fork event: 2

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 12
  • Total pull requests: 31
  • Average time to close issues: 7 months
  • Average time to close pull requests: about 2 months
  • Total issue authors: 3
  • Total pull request authors: 8
  • Average comments per issue: 0.17
  • Average comments per pull request: 0.74
  • Merged pull requests: 19
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 9
  • Pull requests: 29
  • Average time to close issues: about 2 months
  • Average time to close pull requests: 23 days
  • Issue authors: 3
  • Pull request authors: 6
  • Average comments per issue: 0.11
  • Average comments per pull request: 0.72
  • Merged pull requests: 19
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • jvshields (28)
  • Sonu0305 (3)
  • isaacgsmith (2)
  • andrewfullard (1)
  • RyanGroneck (1)
  • smithis7 (1)
Pull Request Authors
  • jvshields (60)
  • RyanGroneck (10)
  • atharva-2001 (9)
  • haydenmonk (5)
  • Sonu0305 (3)
  • smokestacklightnin (2)
  • isaacgsmith (2)
  • KasukabeDefenceForce (2)
  • hmperk18 (1)
  • light2802 (1)
Top Labels
Issue Labels
bug (8) enhancement (2) good first issue (1)
Pull Request Labels
benchmarks (12) documentation (6) git-lfs-pull (3) build-docs (2) bug (1) build_docs (1)