All Projects β†’ spacetelescope β†’ jwql

spacetelescope / jwql

Licence: BSD-3-Clause license
The James Webb Space Telescope Quicklook Application

Programming Languages

python
139335 projects - #7 most used programming language
HTML
75241 projects
Jupyter Notebook
11667 projects
javascript
184084 projects - #8 most used programming language
CSS
56736 projects

Projects that are alternatives of or similar to jwql

ci-testing-python
Sample Microservice App in Python for Testing using pytest, uber/doubles, tox on CI servers like Jenkins and Travis CI using Docker + Docker-Compose for test environment.
Stars: ✭ 37 (-11.9%)
Mutual labels:  jenkins, pytest
Best Of Python Dev
πŸ† A ranked list of awesome python developer tools and libraries. Updated weekly.
Stars: ✭ 243 (+478.57%)
Mutual labels:  sphinx, pytest
Python Blueprint
🐍 Example Python project using best practices πŸ”©
Stars: ✭ 123 (+192.86%)
Mutual labels:  sphinx, pytest
Dicomweb Client
Python client for DICOMweb RESTful services
Stars: ✭ 60 (+42.86%)
Mutual labels:  numpy, pytest
Unittest Xml Reporting
unittest-based test runner with Ant/JUnit like XML reporting.
Stars: ✭ 255 (+507.14%)
Mutual labels:  jenkins, pytest
Machine Learning With Python
Practice and tutorial-style notebooks covering wide variety of machine learning techniques
Stars: ✭ 2,197 (+5130.95%)
Mutual labels:  numpy, pytest
The-Data-Visualization-Workshop
A New, Interactive Approach to Learning Data Visualization
Stars: ✭ 59 (+40.48%)
Mutual labels:  numpy, bokeh
Seleniumbase
A Python framework that inspires developers to become better test automation engineers. πŸ§ πŸ’‘
Stars: ✭ 2,520 (+5900%)
Mutual labels:  jenkins, pytest
pygments-pytest
A pygments lexer for pytest output
Stars: ✭ 23 (-45.24%)
Mutual labels:  sphinx, pytest
pytest-pytorch
pytest plugin for a better developer experience when working with the PyTorch test suite
Stars: ✭ 36 (-14.29%)
Mutual labels:  pytest
docker
collection of docker / docker-compose files, dind, gitlab, jenkins, mongo, mysql, oracle, rabbitmq, redis, sonarqube
Stars: ✭ 25 (-40.48%)
Mutual labels:  jenkins
ai-virtual-mouse
Developed an AI-based system to control the mouse cursor using Python and OpenCV with the real-time camera. Fingertip location is mapped to RGB images to control the mouse cursor.
Stars: ✭ 59 (+40.48%)
Mutual labels:  numpy
github-api-plugin
This plugin packages stock github-api library
Stars: ✭ 20 (-52.38%)
Mutual labels:  jenkins
pyrpipe
Reproducible bioinformatics pipelines in python. Import any Unix tool/command in python.
Stars: ✭ 53 (+26.19%)
Mutual labels:  conda
gcf-packs
Library packs for google cloud functions
Stars: ✭ 48 (+14.29%)
Mutual labels:  numpy
shallow-water
Python model solving the shallow water equations (linear momentum, nonlinear continuity)
Stars: ✭ 78 (+85.71%)
Mutual labels:  numpy
sphinx-themes.org
A showcase for Sphinx documentation themes
Stars: ✭ 114 (+171.43%)
Mutual labels:  sphinx
docker-commons-plugin
API plugin, which provides the common shared functionality for various Docker-related plugins.
Stars: ✭ 38 (-9.52%)
Mutual labels:  jenkins
lovely-pytest-docker
Pytest plugin providing the ability to use docker-compose services as fixtures.
Stars: ✭ 73 (+73.81%)
Mutual labels:  pytest
pytest-localstack
Pytest plugin for local AWS integration tests
Stars: ✭ 66 (+57.14%)
Mutual labels:  pytest

The JWST Quicklook Application (JWQL)

Current Release PyPI - License Python Build Status Documentation Status STScI DOI codecov

The JWST Quicklook Application (JWQL) is a database-driven web application and automation framework for use by the JWST instrument teams to monitor and trend the health, stability, and performance of the JWST instruments. The system is comprised of the following:

  1. A network file system that stores all uncalibrated and calibrated data products on disk in a centrally-located area, accessible to instrument team members (i.e. the MAST data cache)
  2. A relational database that stores observational metadata allowing for data discovery via relational queries (MAST database API).
  3. A software library that provides tools to support an automation framework in which to build automated instrument monitoring routines.
  4. A web application that allows users to visually inspect new and archival JWST data as well as instrument-specific monitoring and performance results.

Official API documentation can be found on ReadTheDocs

The jwql application is available at https://jwql.stsci.edu. Please note that the application is currently restricted to specific JWST instrument team members.

Installation for Users

To install jwql, simply use pip:

pip install jwql

The section below describes a more detailed installation for users that wish to contribute to the jwql repository.

Installation for Contributors

Getting jwql up and running on your own computer requires four steps, detailed below:

  1. Cloning the GitHub repository
  2. Installing the condaenvironment
  3. Installing the python package
  4. Setting up the configuration file

Prerequisites

It is highly suggested that contributors have a working installation of anaconda or miniconda for Python 3.8. Downloads and installation instructions are available here:

Requirements for contributing to the jwql package will be included in the jwql conda environment, which is included in our installation instructions below. Further package requirements will be provided for jwql by a setup.py script included in the repository.

Clone the jwql repo

You first need to clone the current version of jwql. The simplest way to do this is to go to the directory you want your copy of the repository to be in and clone the repository there. Once you are in the directory you can do the following:

git clone https://github.com/spacetelescope/jwql.git
cd jwql

or, if you would rather use SSH instead of https, type

git clone [email protected]:spacetelescope/jwql.git
cd jwql

instead, and then proceed as stated.

Environment Installation

Following the download of the jwql repository, contributors can then install the jwql conda environment via the environment yaml file, which contains all of the dependencies for the project. First, if necessary, install conda. Next, ensure that your version of conda is up to date:

conda update conda

Next, activate the base or root environment (depending on your version of conda):

source activate base/root

Note: If you have added a step activating conda to your default terminal/shell (e.g. the .bashrc, .zshrc, or .profile file) then you don't need to do the above step.

Lastly, create the jwql environment via one of the environment.yml files (currently environment_python_3_8.yml, for python 3.8, and environment_python_3.9.yml, for python 3.9, are supported by jwql):

conda env create -f environment_python_3_8.yml

or

conda env create -f environment_python_3.9.yml

Configuration File

Much of the jwql software depends on the existence of a config.json file within the jwql directory. This file contains data that may be unique to users and/or contain sensitive information. Please see the Config File wiki page for instructions on how to provide this file.

Citation

If you use JWQL for work/research presented in a publication (whether directly, or as a dependency to another package), we recommend and encourage the following acknowledgment:

  This research made use of the open source Python package 'jwql' (Bourque et al, 2020).

where (Bourque et al, 2020) is a citation of the Zenodo record available using the DOI badge above. By using the Export box in the lower right corner of the Zenodo page, you can export the citation in the format most convenient for you.

Software Contributions

There are two current pages to review before you begin contributing to the jwql development. The first is our style guide and the second is our suggested git workflow page, which contains an in-depth explanation of the workflow.

Contributors are also encouraged to check out the Checklist for Contributors Guide to ensure the pull request contains all of the necessary changes.

The following is a bare-bones example of a best work flow for contributing to the project:

  1. Create a fork off of the spacetelescope jwql repository.
  2. Make a local clone of your fork.
  3. Ensure your personal fork is pointing upstream properly.
  4. Create a branch on that personal fork.
  5. Make your software changes.
  6. Push that branch to your personal GitHub repository (i.e. origin).
  7. On the spacetelescope jwql repository, create a pull request that merges the branch into spacetelescope:develop.
  8. Assign a reviewer from the team for the pull request.
  9. Iterate with the reviewer over any needed changes until the reviewer accepts and merges your branch.
  10. Delete your local copy of your branch.

Issue Reporting / Feature Requests

Users who wish to report an issue or request a new feature may do so through the following channels:

  1. Submit a new issue on GitHub (preferred method): https://github.com/spacetelescope/jwql/issues
  2. Submit a new ticket on Jira: https://jira.stsci.edu/projects/JWQL/

Code of Conduct

Users and contributors to the jwql repository should adhere to the Code of Conduct. Any issues or violations pertaining to the Code of Conduct should be brought to the attention of a jwql team member or to [email protected].

Questions

Any questions about the jwql project or its software can be directed to [email protected].

Current Development Team

Past Development Team Members

Acknowledgments:

  • Faith Abney (DMD)
  • Joshua Alexander (DMD) @obviousrebel
  • Anastasia Alexov (DMD)
  • Sara Anderson (DMD)
  • Tracy Beck (INS)
  • Francesca Boffi (INS) @frboffi
  • Clara Brasseur (DMD) @ceb8
  • Matthew Burger (DMD)
  • Steven Crawford (DMD) @stscicrawford
  • James Davies (DMD) @jdavies-st
  • Rosa Diaz (INS) @rizeladiaz
  • Van Dixon (INS)
  • Larry Doering (ITSD)
  • Tom Donaldson (DMD) @tomdonaldson
  • Kim DuPrie (DMD)
  • Jonathan Eisenhamer (DMD) @stscieisenhamer
  • Ben Falk (DMD) @falkben
  • Ann Feild (OPO)
  • Mike Fox (DSMO) @mfox22
  • Scott Friedman (INS)
  • Alex Fullerton (INS) @awfullerton
  • Macarena Garcia Marin (INS)
  • Lisa Gardner (DMD)
  • Vera Gibbs (ITSD)
  • Catherine Gosmeyer (INS) @cgosmeyer
  • Phil Grant (ITSD)
  • Dean Hines (INS)
  • Sherie Holfeltz (INS) @stholfeltz
  • Joe Hunkeler (DMD) @jhunkeler
  • Catherine Kaleida (DMD) @ckaleida
  • Deborah Kenny (DMD)
  • Jenn Kotler (DMD) @jenneh
  • Daniel KΓΌhbacher (Goddard) @DanielKuebi
  • Mark Kyprianou (DMD) @mkyp
  • Stephanie La Massa (INS)
  • Matthew Lallo (INS)
  • Karen Levay (DMD)
  • Crystal Mannfolk (SCOPE) @cmannfolk
  • Greg Masci (ITSD)
  • Jacob Matuskey (DMD) @jmatuskey
  • Margaret Meixner (INS)
  • Christain Mesh (DMD) @cam72cam
  • Prem Mishra (ITSD)
  • Don Mueller (ITSD)
  • Maria Antonia Nieto-Santisteban (SEITO)
  • Brian O'Sullivan (INS)
  • Joe Pollizzi (JWSTMO)
  • Lee Quick (DMD)
  • Anupinder Rai (ITSD)
  • Matt Rendina (DMD) @rendinam
  • Massimo Robberto (INS) @mrobberto
  • Mary Romelfanger (DMD)
  • Elena Sabbi (INS)
  • Bernie Shiao (DMD)
  • Matthew Sienkiewicz (ITSD)
  • Arfon Smith (DSMO) @arfon
  • Linda Smith (INS)
  • Patrick Taylor (ITSD)
  • Dave Unger (ITSD)
  • Jeff Valenti (JWSTMO) @JeffValenti
  • Jeff Wagner (ITSD)
  • Thomas Walker (ITSD)
  • Geoff Wallace (DMD)
  • Lara Wilkinson (OPO)
  • Alex Yermolaev (ITSD) @alexyermolaev
  • Joe Zahn (ITSD)
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].