diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/404.html b/404.html new file mode 100644 index 0000000..e8b1f95 --- /dev/null +++ b/404.html @@ -0,0 +1,602 @@ + + + +
+ + + + + + + + + + + + + + + + + + +This document takes into consideration data that would be collected and made available for dplPy and dendrochronologist to use.
+We will collect tree ring measurements from various tree species in our study area. Data will include tree ring width measurements, corresponding years, and species information. These measurements will be stored in structured CSV and RWL files, with metadata indicating sample location, collection date, and field methods.
+Tree cores will be extracted from trees using increment borers. Ring width measurements will be taken using specialized equipment. Species identification will be done based on field observations and confirmed through lab analysis.
+Tree ring data and associated metadata will be stored in a dedicated directory on our secure research server. Automated daily backups will be conducted to ensure data integrity.
+Data will be organized by sample location, species, and collection year. Each dataset will have an accompanying metadata file detailing data structure, variable definitions, and data processing steps.
+(These metadata files are obtainable when downloading data through the NOAA tree ring archive.)
+Upon project completion, the dataset will be deposited in a recognized tree ring database or repository, ensuring long-term preservation and discoverability (NOAA). The repository will assign a Digital Object Identifier (DOI) for reliable referencing.
+After a brief embargo period to allow for primary analysis, the dataset will be openly accessible through the repository under a Creative Commons Attribution (CC-BY) license, promoting data reuse with proper attribution.
+Ethics approval has been obtained for the study. All data collection follows ethical guidelines, and any potential impact on tree populations or ecosystems will be minimized.
+The lead dendrochronologist will oversee data management, ensuring accuracy and quality. Field technicians will collect core samples and measurements. The institution's data management team will facilitate repository submission.
+Funding has been allocated for specialized dendrochronology equipment, data storage, repository fees, and data management software.
+This Data Management Plan ensures responsible collection, storage, and sharing of tree ring data, in adherence to dendrochronological best practices and ethical standards. It promotes the transparency, reproducibility, and accessibility of tree ring research.
+ +This is a living document. Changes are expected throughout the life of the project.
+This Project Governance document defines operating procedures and rules aimed to clarify and support the involvement of dplPy in FOSS and the FOSS reference hub.
+This section highights the dplPy project on its own and its implementation in the FOSS Reference Hub.
+dplPy is the Python implementation of the OpenDendro project, an open-source framework that aims to provide dendrochronologists with the required analytical software necessary for tree-ring related research. The majority of the code for dplPy was developed by Ifeoluwa Ale, a student Computer Scienctist at the University of Arizona, and supervised by Michele Cosi, Dr. Tyson Swetnam, and Dr. Kevin Anchukaitis. OpenDendro is supervised by Dr. Kevin Anchukaitis, Andy Bunn, Dr. Tyson Swetnam and Dr. Edward Cook.
+The FOSS reference hub is a reference repository for the Foundational Open Science Skills (FOSS) workshop series. Together with dplPy, the aim of this repository is to serve as a reference for the capstone, which FOSS attendees are expected to complete within the duration of the FOSS workshop.
+The dplPy project was selected to enhance the FOSS Reference Hub with a reliable codebase, ensuring it mirrors a genuine repository that participants can use as a model when attempting to replicate similar setups for their individual projects.
+The goals of the FOSS Reference Hub are to: +- Serve as an exemplary reference for a well structured research object. +- Guide FOSS attendees through weekly exercises designed to progressively enhance their project repositories.
+Meet the education team at CyVerse/Data Science Institute:
+With the collaboration of the dplPy team:
+FOSS will also be hosting the following guest speakers:
+FOSS
+├── CyVerse/Data Science Institute
+│ ├── Tyson Swetnam
+│ ├── Jeff Gillan
+│ ├── Carlos Lizarraga
+│ ├── Tina Lee
+│ └── Michele Cosi
+├── FOSS Reference Hub
+│ └── dplPy
+│ ├── Kevin Anchukaitis
+│ ├── Edward Cook
+│ ├── Andy Bunn
+│ └── Ifeuwa Ale
+└── Guest Speakers
+ ├── Jason Williams
+ └── Wade Bishop
+
In order to ensure well distributed work loads across FOSS and the FOSS teaching materials including the FOSS Reference Hub, we have outlined communications and procedure components in order to maximize effectiveness and efficiency.
+Internal communications: communications within the CyVerse/Data Science Institute team is carried out through private Slack channels (CyVerse, CyVerseLearning, Data7) and Zoom meetings.
+External communications: communications to the dplPy team is carried out through a private Slack channel (openDendro), whilst communication to the guest speakers is done through email (Wade Bishop) and the CyVerse/CyverseLearning Slack Channel (Jason Williams).
+Note keeping & attendees: communications to FOSS attendees is achieved through the CyVerseLearning Slack channel. This will allow attendees to share thoughts and notes on lectures and materials during and after the workshop. Note keeping during the workshop is carried out through HackMD, which links are shared during the workshop sessions. All workshops will be done through Zoom, creating a virtual classroom environment allowing remote attendees to take part to the workshop. Recordings of these workshop sessions will be made available to attendees through a private YouTube playlist.
+All of the code base required for FOSS, the FOSS Reference Hub and the dplPy project is stored in their respective GitHub repositories:
+All of these repositories can only be modified by the CyVerse/Data Science Institute team (or the dplPy team regarding the dplPy repository) or through a reviewed pull request. Websites for FOSS (foss.cyverse.org) and OpenDendro (opendendro.org) are created using MkDocs-Material and hosted on GitHub Pages, built through automated GitHub Actions.
+We are committed to Open Science as we operate through transparency, collaboration, and accessibility, guided by theFAIR (Findable, Accessible, Interoperable, Reusable) and CARE (Collective Benefit, Accountability, Responsibility, Equity) principles.
+Our educational materials and publications are thoughtfully curated to align with Open Science ideals. We seek to empower others to adopt and implement Open Science practices, making research more accessible and reproducible.
+As part of the University of Arizona, we acknowledge and respect the land and territories on which we are able to perform our duties as educators with the following statement: We respectfully acknowledge the University of Arizona is on the land and territories of Indigenous peoples. Today, Arizona is home to 22 federally recognized tribes, with Tucson being home to the O’odham and the Yaqui. Committed to diversity and inclusion, the University strives to build sustainable relationships with sovereign Native Nations and Indigenous communities through education offerings, partnerships, and community service.
+We encourage everyone to participate and are committed to building a community for all. +Although we will fail attimes, we seek to treat everyone as fairly and equally as possible. Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, if you are a witness to an event of this nature, it is your responsibility to both listen carefully and respectfully to the victims, as well as to take action to bring attention to the behaviour, and to make every effort to stop the behaviour.
+It is also our responsibility to do our best to right the wrong. +Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.
+In conjunction with for using CyVerse cyberinfrastructure, this Code of Conduct applies to all Event participants and their activities while using CyVerse resources and/or attending the Event.
+CyVerse is dedicated to providing professional computational research and educational experiences for all of our users, regardless of domain focus, academic status, educational level, gender/gender identity/expression, age, sexual orientation, mental or physical ability, physical appearance, body size, race, ethnicity, religion (or lack thereof), technology choices, dietary preferences, or any other personal characteristic.
+When using CyVerse or participating at an Event, we expect you to:
+Interact with others and use CyVerse professionally and ethically by complying with our Policies. +Constructively critize ideas and processes, not people. +Follow the Golden Rule (treat others as you want to be treated) when interacting online or in-person with collaborators, trainers, and support staff. +Comply with this Code in spirit as much as the letter, as it is neither exhaustive nor complete in identifying any and all possible unacceptable conduct. +We do not tolerate harassment of other users or staff in any form (including, but not limited to, violent threats or language, derogatory language or jokes, doxing, insults, advocating for or encouraging any of these behaviors). Sexual language and imagery are not appropriate at any time (excludes Protected Health Information in compliance with HIPAA). Any user violating this Code may be expelled from the platform and the workshop at CyVerse's sole discretion without warning.
+To report a violation of this Code, directly message a trainer via Slack or email info@cyverse.org with the following information:
+Your contact information +Names (real, username, pseudonyms) of any individuals involved, and or witness(es) if any. +Your account of what occurred and if the incident is ongoing. If there is a publicly available record (a tweet, public chat log, etc.), please include a link or attachment. +Any additional information that may be helpful in resolving the issue.
+FOSS teaching materials and FOSS Reference Hub are made available under the CC BY 4.0 License: https://creativecommons.org/licenses/by/4.0/legalcode.
+dplPy and OpenDendro are made available under the GNU General Public Licence v3.0: https://creativecommons.org/licenses/by/4.0/legalcode
+We kindly ask to respect the Licences by which this material is developed.
+ +{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Ha=/["'&<>]/;Un.exports=$a;function $a(e){var t=""+e,r=Ha.exec(t);if(!r)return t;var o,n="",i=0,s=0;for(i=r.index;i