deploy: 28c84d2

.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: b0d0fdfd2d836ecb09ef341e180cbeb8
+tags: 645f666f9bcd5a90fca523b33c5a78b7

_sources/code_of_conduct.md

@@ -0,0 +1,135 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+  [email protected] .
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

_sources/intro.md

@@ -0,0 +1,128 @@
+---
+# File metadata may be provided as frontmatter YAML
+title: Global Fish Tracking System (GFTS) 
+subtitle: DESP Use case
+description: Making fishing more sustainable 
+date: 2023-12-12
+authors:
+  - id: yellowcap
+    name: Daniel Wiesmann
+    orcid: 0000-0002-3190-4278
+    corresponding: true
+    email: [email protected] 
+    roles:
+      - Lead
+      - User Interface
+    affiliations:
+      - developmentseed
+  - id: olafveerman
+    name: Olaf Veerman
+    orcid: 0000-0002-5408-9923
+    corresponding: false
+    roles:
+      - Lead
+    affiliations:
+      - developmentseed
+  - id: danielfdsilva
+    name: Daniel da Silva
+    orcid: 0009-0002-4476-7927
+    corresponding: false
+    roles:
+      - User Interface
+    affiliations:
+      - developmentseed
+  - id: ricardoduplos
+    name: Ricardo Mestre
+    orcid: 
+    corresponding: false
+    roles:
+      - User Interface
+    affiliations:
+      - developmentseed
+  - id: annefou
+    name: Anne Fouilloux
+    orcid: 0000-0002-1784-2920
+    corresponding: false
+    roles:
+      - Infrastructure
+    affiliations:
+      - simula
+  - id: minrk
+    name: Benjamin Ragan-Kelley
+    orcid: 0000-0002-1023-7082
+    corresponding: false
+    roles:
+      - Infrastructure
+    affiliations:
+      - simula
+  - id: tinaok
+    name: Tina Erica Odaka
+    orcid: 0000-0002-1500-0156
+    corresponding: false
+    roles:
+      - Modelling
+    affiliations:
+      - ifremer
+  - id: mwoillez
+    name: Mathieu Woillez
+    orcid: 0000-0002-1032-2105
+    corresponding: false
+    roles:
+      - Modelling
+    affiliations:
+      - ifremer
+  - id: emmanuelleautret 
+    name: Emmanuelle Autret
+    orcid: 0000-0002-0979-9192
+    corresponding: false
+    roles:
+      - Modelling
+    affiliations:
+      - ifremer
+affiliations:
+  - id: simula
+    name: Simula Research Laboratory
+    city: Oslo
+    country: Norway
+    url: https://www.simula.no
+    ror: https://ror.org/00vn06n10
+  - id: developmentseed
+    name: Development Seed
+    city: Lisbon
+    country: Portugal
+  - id: ifremer
+    name: IFREMER
+    city: Brest
+    country: France
+    url: https://www.ifremer.fr
+    ror: https://ror.org/044jxhp58
+tags:
+  - oceanography
+  - digital-twin
+  - destination-earth
+thumbnail: images/gfts.png
+---
+
+
++++ {"part":"abstract"}
+
+% The article should include an abstract block at the beginning. The block is delimited by `+++` before and after, and you must specify `"part": "abstract"` as JSON metadata on the block opener. This metadata is required for recognizing the content of this cell as the abstract.
+% The abstract should begin with a short description of the problem addressed, briefly describe the new data or analyses, then briefly state the main conclusion(s) and how they are supported, and address any uncertainty.
+
+This project entails the implementation of an advanced fish tracking system utilizing biologging data and high-resolution ocean temperature and bathymetry. Employing state-of-the-art modeling techniques and large-scale cloud computing, the initiative focuses on accurately estimating the movement of tagged fish. Additionally, a Decision Support Tool will be developed to present modeling outputs in an intuitive manner, catering to the needs of decision-makers in fisheries management.
+
++++
+
+# Overview of GFTS DESP use case
+
+<style>
+.responsive-wrap iframe{ max-width: 100%;}
+</style>
+<div class="responsive-wrap">
+<!-- this is the embed code provided by Google -->
+  <iframe src="https://docs.google.com/presentation/d/1DMa__GRQXhpkqx4VNWDgHdYr_Z2SsWkc_j3m2E01GUs/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
+<!-- Google embed ends -->
+</div>
+
+
+

_sphinx_design_static/design-tabs.js

@@ -0,0 +1,27 @@
+var sd_labels_by_text = {};
+
+function ready() {
+  const li = document.getElementsByClassName("sd-tab-label");
+  for (const label of li) {
+    syncId = label.getAttribute("data-sync-id");
+    if (syncId) {
+      label.onclick = onLabelClick;
+      if (!sd_labels_by_text[syncId]) {
+        sd_labels_by_text[syncId] = [];
+      }
+      sd_labels_by_text[syncId].push(label);
+    }
+  }
+}
+
+function onLabelClick() {
+  // Activate other inputs with the same sync id.
+  syncId = this.getAttribute("data-sync-id");
+  for (label of sd_labels_by_text[syncId]) {
+    if (label === this) continue;
+    label.previousElementSibling.checked = true;
+  }
+  window.localStorage.setItem("sphinx-design-last-tab", syncId);
+}
+
+document.addEventListener("DOMContentLoaded", ready, false);