ivert 0.6.0__tar.gz

ivert-0.6.0/.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+    cooldown:
+      default-days: 7
+    groups:
+      gha-dependencies:
+        patterns:
+          - "*"

ivert-0.6.0/.github/workflows/codacy.yml

@@ -0,0 +1,61 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+# This workflow checks out code, performs a Codacy security scan
+# and integrates the results with the
+# GitHub Advanced Security code scanning feature.  For more information on
+# the Codacy security scan action usage and parameters, see
+# https://github.com/codacy/codacy-analysis-cli-action.
+# For more information on Codacy Analysis CLI in general, see
+# https://github.com/codacy/codacy-analysis-cli.
+
+name: Codacy Security Scan
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [ "main" ]
+  schedule:
+    - cron: '17 11 * * 6'
+
+permissions:
+  contents: read
+
+jobs:
+  codacy-security-scan:
+    permissions:
+      contents: read # for actions/checkout to fetch code
+      security-events: write # for github/codeql-action/upload-sarif to upload SARIF results
+      actions: read # only required for a private repository by github/codeql-action/upload-sarif to get the Action run status
+    name: Codacy Security Scan
+    runs-on: ubuntu-latest
+    steps:
+      # Checkout the repository to the GitHub Actions runner
+      - name: Checkout code
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5  # v4
+
+      # Execute Codacy Analysis CLI and generate a SARIF output with the security issues identified during the analysis
+      - name: Run Codacy Analysis CLI
+        uses: codacy/codacy-analysis-cli-action@d840f886c4bd4edc059706d09c6a1586111c540b
+        with:
+          # Check https://github.com/codacy/codacy-analysis-cli#project-token to get your project token from your Codacy repository
+          # You can also omit the token and run the tools that support default configurations
+          project-token: ${{ secrets.CODACY_PROJECT_TOKEN }}
+          verbose: true
+          output: results.sarif
+          format: sarif
+          # Adjust severity of non-security issues
+          gh-code-scanning-compat: true
+          # Force 0 exit code to allow SARIF file generation
+          # This will handover control about PR rejection to the GitHub side
+          max-allowed-issues: 2147483647
+
+      # Upload the SARIF file generated in the previous step
+      - name: Upload SARIF results file
+        uses: github/codeql-action/upload-sarif@02c5e83432fe5497fd85b873b6c9f16a8578e1d9  # v3
+        with:
+          sarif_file: results.sarif

ivert-0.6.0/.github/workflows/publish-to-pypi.yml

@@ -0,0 +1,69 @@
+name: "Build & publish to PyPI"
+
+on:
+  pull_request:
+  release:
+    types:
+      # Triggers when you click "Publish release" in GitHub
+      - "published"
+
+permissions: {}
+
+jobs:
+  build:
+    name: "Build"
+    runs-on: "ubuntu-latest"
+    steps:
+    - name: "Checkout code"
+      uses: "actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd"  # v6.0.2
+      with:
+        persist-credentials: false
+
+    - name: "Set up Python"
+      uses: "actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405"  # v6.2.0
+      with:
+        python-version: "3.x"
+
+    - name: "Install build tools"
+      run: |
+        python -m pip install --upgrade pip
+        pip install build
+
+    - name: "Build package"
+      run: "python -m build"
+
+    - uses: "prefix-dev/setup-pixi@ba3bb36eb2066252b2363392b7739741bb777659"  # v0.8.1
+      with:
+        run-install: false
+
+    - name: "Test built package"
+      shell: "pixi exec --list --spec libgdal-core -- bash -e {0}"
+      run: |
+        python -m pip install dist/*.whl
+        cd /tmp
+        python -c "import ivert; print(f'Version: {ivert.__version__}')"
+        ivert --version
+
+    - uses: "actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f"  # v7.0.0
+      with:
+        name: "dist"
+        path: "dist/"
+
+  pypi-publish:
+    name: "Publish to PyPI"
+    runs-on: "ubuntu-latest"
+    if: "github.event_name == 'release'"
+    needs: "build"
+    environment:
+      name: "pypi"
+      url: "https://pypi.org/p/ivert"
+    permissions:
+      id-token: "write"
+    steps:
+    - name: "Get dist artifact"
+      uses: "actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c"  # v8.0.1
+      with:
+        name: "dist"
+        path: "dist/"
+    - name: "Publish to PyPI"
+      uses: "pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b"  # release/v1

ivert-0.6.0/.github/workflows/zizmor.yml

@@ -0,0 +1,29 @@
+name: "GitHub Actions Security Analysis with zizmor 🌈"
+
+on:
+  push:
+    branches:
+      - "main"
+    paths:
+      - ".github/workflows/*"
+  pull_request:
+    paths:
+      - ".github/workflows/*"
+
+
+permissions: {}
+
+jobs:
+  zizmor:
+    name: "Run zizmor 🌈"
+    runs-on: "ubuntu-latest"
+    permissions:
+      security-events: "write" # Required for upload-sarif (used by zizmor-action) to upload SARIF files.
+    steps:
+      - name: "Checkout repository"
+        uses: "actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0" # v7.0.0
+        with:
+          persist-credentials: false
+
+      - name: "Run zizmor 🌈"
+        uses: "zizmorcore/zizmor-action@192e21d79ab29983730a13d1382995c2307fbcaa" # v0.5.7

ivert-0.6.0/.gitignore

@@ -0,0 +1,169 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+_version.py
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+data/*
+scratch_data/*
+src/tests/
+src/tests_old/
+
+# Any project-specific Claude Code helper files.
+CLAUDE.md
+.claude/

ivert-0.6.0/.pre-commit-config.yaml

@@ -0,0 +1,27 @@
+ci:
+  autoupdate_schedule: quarterly
+  autofix_prs: false
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: forbid-new-submodules
+      - id: end-of-file-fixer
+      - id: check-case-conflict
+      - id: requirements-txt-fixer
+      - id: check-added-large-files
+        args: ['--maxkb=500']
+      - id: check-json
+      - id: check-toml
+      - id: check-yaml
+      - id: debug-statements
+      - id: check-builtin-literals
+      - id: trailing-whitespace
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.9
+    hooks:
+      - id: ruff-check
+        args: ['--fix']
+      - id: ruff-format

ivert-0.6.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 CIRES Coastal DEM Group
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

ivert-0.6.0/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.4
+Name: ivert
+Version: 0.6.0
+Summary: The ICESat-2 Validation of Elevations Reporting Tool (IVERT)
+Project-URL: Source, https://github.com/ciresdem/IVERT
+Author-email: Michael MacFerrin <michael.macferrin@colorado.edu>
+License: MIT License
+        
+        Copyright (c) 2023 CIRES Coastal DEM Group
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+License-File: LICENSE
+Keywords: Geospatial
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.12
+Requires-Dist: blosc2
+Requires-Dist: click
+Requires-Dist: dateparser
+Requires-Dist: fetchez
+Requires-Dist: gdal
+Requires-Dist: geopandas
+Requires-Dist: globato
+Requires-Dist: h5py
+Requires-Dist: matplotlib
+Requires-Dist: netcdf4
+Requires-Dist: numexpr
+Requires-Dist: numpy
+Requires-Dist: packaging
+Requires-Dist: pandas
+Requires-Dist: psutil
+Requires-Dist: pyproj
+Requires-Dist: rasterio
+Requires-Dist: scipy
+Requires-Dist: shapely
+Requires-Dist: six
+Requires-Dist: tabulate
+Requires-Dist: transformez
+Requires-Dist: xarray
+Description-Content-Type: text/markdown
+
+# IVERT
+**ICESat-2 Validation of Elevations Reporting Tool**
+
+IVERT validates Digital Elevation Models (DEMs) by comparing their elevations against ICESat-2 satellite photon data. It supports topographic, bathymetric, and mixed coastal DEMs, runs fully offline on any machine, and handles vertical datum conversions automatically.
+
+Developed by the [CIRES Coastal DEM Team](https://ciresdem.github.io). Primary authors: [Mike MacFerrin](https://github.com/mmacferrin) (IVERT) and [Matthew Love](https://github.com/matth-love) ([continuous-dems](https://github.com/continuous-dems) utilities).
+
+> **Note:** This repository will soon be ported over to the [continuous-dems](https://github.com/continuous-dems) ecosystem.
+
+---
+
+(TODO: Add some pretty pictures here)
+
+---
+
+## Capabilities
+
+- Validate topographic, bathymetric, and coastal DEMs against ICESat-2 ATL03/ATL24 photons
+- Combines [ATL03](https://nsidc.org/data/atl03/)/[ATL08](https://nsidc.org/data/atl08/)/[ATL13](https://nsidc.org/data/atl13/)/[ATL24](https://nsidc.org/data/atl24/) for photon-level classifications, plus external datasets (such as the [Global Buildings Atlas](https://tubvsig-so2sat-vm1.srv.mwn.de/)) to classify built structures.
+- Additional coastline filtering to minimize false-positive ATL08 "ground" photons appearing offshore over water, and unreasonably-shallow "bathy floor" photons with large errors over deep water. 
+- Automatic vertical datum conversions (NAVD88, EGM2008, MLLW, and many more)
+- Configurable photon confidence and quality filtering
+- Statistical outputs: bias, RMSE, NMAD, per-cell error maps
+- Automatically-generated plots of DEM accuracies compared to ICESat-2.
+- Export errors to GeoTIFF, GeoPackage, Shapefile, or XYZ text
+- Local photon database management — download once, validate many times
+
+---
+
+## Installation
+
+```bash
+pip install ivert
+```
+(^ coming soon)
+
+For development (editable install from this repo):
+
+```bash
+git clone https://github.com/ciresdem/IVERT.git
+cd IVERT
+pip install -e .
+```
+
+Three dependencies — `fetchez`, `globato`, and `transformez` — are pulled automatically from the [continuous-dems](https://github.com/continuous-dems) GitHub organization and do not need to be installed separately.
+
+---
+
+## Quick start
+
+**1. Download ICESat-2 photon data for your area** (bounding box in W/E/S/N order):
+
+```bash
+ivert database download -- -74.0/-73.0/40.5/41.0
+```
+
+**2. Validate your DEM:**
+
+```bash
+ivert validate mydem.tif
+```
+
+**3. Check the output directory** for `mydem_results.h5`, a validation plot (`.png`), and error exports (`.tif`, `.gpkg`).
+
+---
+
+## Documentation
+
+| Command | Description |
+|---------|-------------|
+| [ivert validate](docs/validate.md) | Validate DEMs against ICESat-2 data |
+| [ivert database](docs/database.md) | Download and manage the local photon database |
+| [ivert cache](docs/cache.md) | View and clear the local file cache |
+| [ivert options](docs/options.md) | View and change configuration settings |
+| [ivert upgrade](docs/upgrade.md) | Upgrade IVERT to the latest version |

ivert-0.6.0/README.md

@@ -0,0 +1,75 @@
+# IVERT
+**ICESat-2 Validation of Elevations Reporting Tool**
+
+IVERT validates Digital Elevation Models (DEMs) by comparing their elevations against ICESat-2 satellite photon data. It supports topographic, bathymetric, and mixed coastal DEMs, runs fully offline on any machine, and handles vertical datum conversions automatically.
+
+Developed by the [CIRES Coastal DEM Team](https://ciresdem.github.io). Primary authors: [Mike MacFerrin](https://github.com/mmacferrin) (IVERT) and [Matthew Love](https://github.com/matth-love) ([continuous-dems](https://github.com/continuous-dems) utilities).
+
+> **Note:** This repository will soon be ported over to the [continuous-dems](https://github.com/continuous-dems) ecosystem.
+
+---
+
+(TODO: Add some pretty pictures here)
+
+---
+
+## Capabilities
+
+- Validate topographic, bathymetric, and coastal DEMs against ICESat-2 ATL03/ATL24 photons
+- Combines [ATL03](https://nsidc.org/data/atl03/)/[ATL08](https://nsidc.org/data/atl08/)/[ATL13](https://nsidc.org/data/atl13/)/[ATL24](https://nsidc.org/data/atl24/) for photon-level classifications, plus external datasets (such as the [Global Buildings Atlas](https://tubvsig-so2sat-vm1.srv.mwn.de/)) to classify built structures.
+- Additional coastline filtering to minimize false-positive ATL08 "ground" photons appearing offshore over water, and unreasonably-shallow "bathy floor" photons with large errors over deep water. 
+- Automatic vertical datum conversions (NAVD88, EGM2008, MLLW, and many more)
+- Configurable photon confidence and quality filtering
+- Statistical outputs: bias, RMSE, NMAD, per-cell error maps
+- Automatically-generated plots of DEM accuracies compared to ICESat-2.
+- Export errors to GeoTIFF, GeoPackage, Shapefile, or XYZ text
+- Local photon database management — download once, validate many times
+
+---
+
+## Installation
+
+```bash
+pip install ivert
+```
+(^ coming soon)
+
+For development (editable install from this repo):
+
+```bash
+git clone https://github.com/ciresdem/IVERT.git
+cd IVERT
+pip install -e .
+```
+
+Three dependencies — `fetchez`, `globato`, and `transformez` — are pulled automatically from the [continuous-dems](https://github.com/continuous-dems) GitHub organization and do not need to be installed separately.
+
+---
+
+## Quick start
+
+**1. Download ICESat-2 photon data for your area** (bounding box in W/E/S/N order):
+
+```bash
+ivert database download -- -74.0/-73.0/40.5/41.0
+```
+
+**2. Validate your DEM:**
+
+```bash
+ivert validate mydem.tif
+```
+
+**3. Check the output directory** for `mydem_results.h5`, a validation plot (`.png`), and error exports (`.tif`, `.gpkg`).
+
+---
+
+## Documentation
+
+| Command | Description |
+|---------|-------------|
+| [ivert validate](docs/validate.md) | Validate DEMs against ICESat-2 data |
+| [ivert database](docs/database.md) | Download and manage the local photon database |
+| [ivert cache](docs/cache.md) | View and clear the local file cache |
+| [ivert options](docs/options.md) | View and change configuration settings |
+| [ivert upgrade](docs/upgrade.md) | Upgrade IVERT to the latest version |

ivert-0.6.0/archive/README.md

@@ -0,0 +1,7 @@
+# Archive
+
+These files are deprecated from previous versions of IVERT and are not currently in use.
+They are retained for reference in case cloud/server features are re-integrated in the future.
+
+- `src/` — archived Python source modules
+- `config/` — archived configuration files and templates

ivert-0.6.0/archive/config/email_templates.ini

@@ -0,0 +1,80 @@
+[DEFAULT]
+# email_templates.ini -- Email templates for IVERT, using the SNS notification system (see sns.py)
+
+# Subject line for when a job is submitted and detected on the EC2.
+# 0: username,
+# 1: job_id
+subject_job_submitted = "IVERT: Job {0}_{1} has been created"
+
+# Generic email intro from IVERT.
+email_ending = """This is an automated message from the ICESat-2 Validation of Elevations Reporting Tool (IVERT). Do not reply to this message.
+ """
+
+# Email template to send out when a job is submitted and detected on the EC2.
+# 0: username,
+# 1: job_id
+# 2: full command being processed
+email_job_submitted = """
+ Your IVERT job "{0}_{1}" has been created and queued for processing.
+
+ The following IVERT command is being run on the EC2 server:
+ {2}
+
+ You can monitor the status of your job at any time by running "ivert status {0}_{1}" at the command line.
+
+ You should get another email when the job is complete and results (if any) are ready to download.
+ """
+
+# May re-include this line if/when we get a 'kill' option implemented to stop/kill an src job.
+#  If you wish to cancel this job, run "src kill {0}_{1}" at the command line and it will be terminated when the EC2 receives the notification. All files uploaded with the job will be deleted. Output files already exported will remain for 7 days before being deleted.
+
+# Subject line for when a job is finished.
+# 0: username,
+# 1: job_id
+# 2: "completed successfully", "completed with partial success", "terminated unexpectedly", or "been killed"
+subject_job_finished = "IVERT: Job {0}_{1} has finished with status '{2}'"
+
+# Email template to send out if the job is finished without any exports.
+# 0: username,
+# 1: job_id
+# 2: The status from the ivert_jobs table of the finished job.
+email_job_finished_start = """
+ Your IVERT job "{0}_{1}" has finished with status '{2}'.
+ """
+
+# 0: number of input files processed (not including the Config file)
+# 1: number of input files processed successfully.
+# 2: number of input files processed unsuccessfully (errors, etc)
+email_job_finished_input_files_addendum = """
+ {0} input files ({1} successful, {2} unsuccessful):
+ """
+
+# 0: The file name
+# 1: The file size
+# 2: The file status
+file_item = """  - {0}, {1}: '{2}'
+ """
+
+# 0: number of total output files.
+# 1: number of output files processed successfully.
+# 2: number of output files processed unsuccessfully (errors, etc)
+email_job_finished_output_files_addendum = """
+ {0} output files ({1} successful, {2} unsuccessful):
+ """
+
+# Addendum of there are any files available to download.
+# 0: username
+# 1: job_id
+email_output_files_download_notification = """
+ You can download the output files by running "ivert download {0}_{1}" at the command line. Files will be availabe online for 7 days before being deleted.
+ """
+
+# An addendum to add if any files were not completed successfully, or if the job itself was unsuccessful or
+# terminated abruptly.
+# 0: username,
+# 1: job_id
+email_job_finished_unsuccessful_addendum = """
+ If the job was unsuccessful or any files were not completed successfully, you may download a
+ detailed logfile by running "ivert download {0}_{1}" at the command line.
+ You can forward this email to your IVERT developers to debug and fix the issue.
+ """