Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spelling #194

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ COSMO is made up of a series of monitors and their data built on the light-weigh
[monitorframe framework](https://github.com/spacetelescope/monitor-framework).
These monitors are important for ensuring that COS is operating nominally as well as extending its mission lifetime.

Check out the COSMO documenation [here](https://spacetelescope.github.io/cosmo/)
Check out the COSMO documentation [here](https://spacetelescope.github.io/cosmo/)

## Contributing
Please open a new [issue](https://github.com/spacetelescope/cosmo/issues) or new
Expand Down
2 changes: 1 addition & 1 deletion cosmo/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
'database': os.environ.get('COSMO_SMS_DB', 'sms.db'),
'pragmas': {
'journal_mode': os.environ.get('COSMO_SMS_DB_JOURNAL', 'wal'),
'foreign_keys': os.environ.get('COSMO_SMS_DB_FORIEGN_KEYS', 1),
'foreign_keys': os.environ.get('COSMO_SMS_DB_FOREIGN_KEYS', 1),
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

API break

'ignore_check_constraints': os.environ.get('COSMO_SMS_DB_IGNORE_CHECK_CONSTRAINTS', 0),
'synchronous': os.environ.get('COSMO_SMS_DB_SYNCHRONOUS', 0)
}
Expand Down
2 changes: 1 addition & 1 deletion cosmo/monitors/jitter_monitors.py
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ def view_jitter(jitter_file: str) -> go.Figure:
{
'title': f'{os.path.basename(jitter_file)} {jitter_data[0]["CONFIG"]}',
'xaxis': {'title': 'Datetime'},
'yaxis': {'title': 'V2 Jitter (averaged over 3 seconds) [arceconds]'},
'yaxis': {'title': 'V2 Jitter (averaged over 3 seconds) [arcseconds]'},
'xaxis2': {'title': 'Datetime'},
'yaxis2': {'title': 'V3 Jitter (averaged over 3 seconds) [arcseconds]'}
}
Expand Down
6 changes: 3 additions & 3 deletions cosmo/monitors/osm_shift_monitors.py
Original file line number Diff line number Diff line change
Expand Up @@ -36,11 +36,11 @@ def compute_segment_diff(df: pd.DataFrame, shift: str, segment1: str, segment2:
# absolute time calculated from FUVA
lamp_time = absolute_time(df=group[group.SEGMENT == segment1])

segmnet1_df, segment2_df = group[group.SEGMENT == segment1], group[group.SEGMENT == segment2]
segment1_df, segment2_df = group[group.SEGMENT == segment1], group[group.SEGMENT == segment2]

# Use the FUVA dataframe to create a "results" dataframe
diff_df = segmnet1_df.assign(
seg_diff=segmnet1_df[shift].values - segment2_df[shift].values
diff_df = segment1_df.assign(
seg_diff=segment1_df[shift].values - segment2_df[shift].values
).reset_index(drop=True)

diff_df['lamp_time'] = lamp_time.to_datetime()
Expand Down
2 changes: 1 addition & 1 deletion docs/source/api.rst
Original file line number Diff line number Diff line change
Expand Up @@ -754,7 +754,7 @@ Cosmo also contains other modules used in supporting either the monitors or data
.. py:class:: JitterFileData(*args, **kwargs)

Class for getting requested data from COS Jitter files (either acq jitter files or association jitter files).
Since association Jitter files have data for multiple exposures across exensions, ``JitterFileData`` subclasses the
Since association Jitter files have data for multiple exposures across extensions, ``JitterFileData`` subclasses the
python ``list`` and instances are equivalent to a list of ``FileData`` dictionaries (one per extension) to enable
collecting requested data for each included exposure.

Expand Down
2 changes: 1 addition & 1 deletion docs/source/monitors.rst
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The following monitors are executed at a *monthly* cadence:
- ``AcqPeakdMonitor``
- ``AcqPeakxdMonitor``
- ``AcqImageV2V3Monitor``
- ``FuvOsmShift1Moniotr``
- ``FuvOsmShift1Monitor``
- ``FuvOsmShift2Monitor``
- ``NuvOsmShift1Monitor``
- ``NuvOsmShift2Monitor``
Expand Down
2 changes: 1 addition & 1 deletion docs/source/sms.rst
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ comments):

COSMO_SMS_DB # 'sms.db'
COSMO_SMS_DB_JOURNAL # 'wal'
COSMO_SMS_DB_FORIEGN_KEYS # 1
COSMO_SMS_DB_FOREIGN_KEYS # 1
COSMO_SMS_DB_IGNORE_CHECK_CONSTRAINTS # 0
COSMO_SMS_DB_SYNCHRONOUS # 0

Expand Down