You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+19-22
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,14 @@
15
15
16
16
17
17
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:
18
-
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 (MAST data cache)
18
+
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)
19
19
2. A relational database that stores observational metadata allowing for data discovery via relational queries (MAST database API).
20
20
3. A software library that provides tools to support an automation framework in which to build automated instrument monitoring routines.
21
21
4. A web application that allows users to visually inspect new and archival JWST data as well as instrument-specific monitoring and performance results.
22
22
23
23
Official API documentation can be found on [ReadTheDocs](https://jwql.readthedocs.io)
24
24
25
-
The `jwql` application is currently under heavy development. The `1.0` release is expected in 2021. Currently, a development version of the web application can be found at [https://dljwql.stsci.edu](https://dljwql.stsci.edu).
25
+
The `jwql` application is available at [https://jwql.stsci.edu](https://jwql.stsci.edu). Please note that the application is currently restricted to specific JWST instrument team members.
26
26
27
27
## Installation for Users
28
28
@@ -44,7 +44,7 @@ Getting `jwql` up and running on your own computer requires four steps, detailed
44
44
45
45
### Prerequisites
46
46
47
-
It is highly suggested that contributors have a working installation of `anaconda` or `miniconda` for Python 3.7. Downloads and installation instructions are available here:
47
+
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:
48
48
49
49
-[Miniconda](https://conda.io/miniconda.html)
50
50
-[Anaconda](https://www.continuum.io/downloads)
@@ -69,7 +69,7 @@ instead, and then proceed as stated.
69
69
70
70
### Environment Installation
71
71
72
-
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, ensure that your version of `conda` is up to date:
72
+
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`](https://docs.conda.io/projects/conda/en/latest/user-guide/install/index.html). Next, ensure that your version of `conda` is up to date:
73
73
74
74
```
75
75
conda update conda
@@ -81,26 +81,19 @@ Next, activate the `base` or `root` environment (depending on your version of `c
81
81
source activate base/root
82
82
```
83
83
84
-
Lastly, create the `jwql` environment via the `environment_python_3_7.yml` file:
84
+
**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.
Next, you need to install the `jwql` package under development mode. This can be accomplished either by running the `setup.py` script, or `pip install` with the `-e` option:
86
+
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`):
93
87
94
88
```
95
-
python setup.py develop
89
+
conda env create -f environment_python_3_8.yml
96
90
```
97
91
98
92
or
99
93
100
94
```
101
-
pip install -e .
95
+
conda env create -f environment_python_3.9.yml
102
96
```
103
-
The package should now appear if you run `conda list jwql`.
104
97
105
98
### Configuration File
106
99
@@ -112,7 +105,9 @@ Much of the `jwql` software depends on the existence of a `config.json` file wit
112
105
If you use `JWQL` for work/research presented in a publication (whether directly,
113
106
or as a dependency to another package), we recommend and encourage the following acknowledgment:
114
107
115
-
This research made use of the open source Python package JWQL (Bourque et al, 2020).
108
+
```
109
+
This research made use of the open source Python package 'jwql' (Bourque et al, 2020).
110
+
```
116
111
117
112
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.
118
113
@@ -127,7 +122,7 @@ The following is a bare-bones example of a best work flow for contributing to th
127
122
128
123
1. Create a fork off of the `spacetelescope``jwql` repository.
129
124
2. Make a local clone of your fork.
130
-
3. Ensure your personal fork is pointing `upstream` properly.
125
+
3. Ensure your personal fork is [pointing `upstream` properly](https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork).
131
126
4. Create a branch on that personal fork.
132
127
5. Make your software changes.
133
128
6. Push that branch to your personal GitHub repository (i.e. `origin`).
@@ -155,19 +150,21 @@ Any questions about the `jwql` project or its software can be directed to `jwql@
155
150
156
151
157
152
## Current Development Team
158
-
- Matthew Bourque (INS) [@bourque](https://github.com/bourque)
0 commit comments