Block Inversion Modeling using TDEFNODE Software
This is the TDEFNODE block inversion software used in the study "Constraining the Kinematics of the Victoria Microplate and the Northern Western Branch of the East African Rift System; The software is installed and run on a Linux terminal. All the files needed to run TDEFNODE for this study, along with their outputs, are included in TDEFNODE_block_inversion_modeling_NWB_Kwagalakwe_2025_v2.tar.gz, which is a revised version of TDEFNODE_block_inversion_modeling_NWB_Kwagalakwe_2025.tar.gz (Version v1).
more »
« less
- Award ID(s):
- 2021633
- PAR ID:
- 10650410
- Publisher / Repository:
- Zenodo
- Date Published:
- Format(s):
- Medium: X
- Right(s):
- Creative Commons Attribution 4.0 International
- Sponsoring Org:
- National Science Foundation
More Like this
-
PhyloFisher is a software package, written in Python3, that contains a protocol designed for phylogenomic dataset assembly and data exploration. This software package aids in the construction and curation of protein sequence-based phylogenomic datasets, conducts post-assembly analyses, and allows visualization of the results. In addition, PhyloFisher currently includes a manually curated starting dataset of 240 proteins from 304 eukaryotic taxa representing the full breadth of known diversity in the eukaryotic tree of life. Importantly, this dataset also includes identified paralogs of each of the 240 proteins from all investigated taxa which is crucial for the identification of probable orthologs. Although PhyloFisher includes this pan-eukaryotic dataset, the tool is flexible and can work with any dataset consisting of protein sequences derived from eukaryotes. The combination of all of the foregoing features makes PhyloFisher a broadly-useful, user-friendly software tool for sophisticated phylogenomic analyses of eukaryotes.</div></div>PROJECT WEBSITE: http://amoeba.msstate.edu/phylofisher/ </div>PROJECT GITHUB: http://github.com/TheBrownLab/PhyloFisher</div></div>This dataset contains files for endusers to retrieve for installation of PhyloFisher as well as accompanying data from the PhyloFisher manuscript.</div></div>Tice_etal.PhyloFisher.archives.tar.gz | Installation requirements for PIP installation</div>Tice_etal.PhyloFisher1.FINAL_DATASET_RENAMED.tar.gz | File dataset associated with the manuscript including matrices and phylogenetic analyses</div>Tice_etal.PhyloFisher_v1.0_input_proteomes_LongNames.tar.gz | Input proteome data from taxa that was used to construct PhyloFisher v1.0</div>Tice_etal.PhyloFisherDatabase_v1.0_Jan.28.2021.tar.gz | PhyloFisher v1.0 starting database</div>Tice_etal.PhyloFisher_FOR_CUSTOM_DATASET_Jan.28.2021.tar.gz | Necessary files and directory structure to be used in custom database construction.</div>Tice_etal.PhyloFisher.DATA.tgz | All data associated with the figures (Fig 3, 4, A-Y) along with all phylogenomic trees and analyses. </div></div></div>more » « less
-
Flaky tests are tests that can non-deterministically pass or fail for the same code version. These tests undermine regression testing efficiency, because developers cannot easily identify whether a test fails due to their recent changes or due to flakiness. Ideally, one would detect flaky tests right when flakiness is introduced, so that developers can then immediately remove the flakiness. Some software organizations, e.g., Mozilla and Netflix, run some tools—detectors—to detect flaky tests as soon as possible. However, detecting flaky tests is costly due to their inherent non-determinism, so even state-of-the-art detectors are often impractical to be used on all tests for each project change. To combat the high cost of applying detectors, these organizations typically run a detector solely on newly added or directly modified tests, i.e., not on unmodified tests or when other changes occur (including changes to the test suite, the code under test, and library dependencies). However, it is unclear how many flaky tests can be detected or missed by applying detectors in only these limited circumstances. To better understand this problem, we conduct a large-scale longitudinal study of flaky tests to determine when flaky tests become flaky and what changes cause them to become flaky. We apply two state-of-theart detectors to 55 Java projects, identifying a total of 245 flaky tests that can be compiled and run in the code version where each test was added. We find that 75% of flaky tests (184 out of 245) are flaky when added, indicating substantial potential value for developers to run detectors specifically on newly added tests. However, running detectors solely on newly added tests would still miss detecting 25% of flaky tests. The percentage of flaky tests that can be detected does increase to 85% when detectors are run on newly added or directly modified tests. The remaining 15% of flaky tests become flaky due to other changes and can be detected only when detectors are always applied to all tests. Our study is the first to empirically evaluate when tests become flaky and to recommend guidelines for applying detectors in the future.more » « less
-
This is the AmeriFlux Management Project (AMP) created FLUXNET-1F version of the carbon flux data for the site US-ICh Imnavait Creek Watershed Heath Tundra. This is the FLUXNET version of the carbon flux data for the site US-ICh Imnavait Creek Watershed Heath Tundra produced by applying the standard ONEFlux (1F) software. Site Description - The Imnavait Creek Watershed Heath Tundra (Ridge Station) is located near Imnavait Creek in Alaska, north of the Brooks Range in the Kuparuk basin near Lake Toolik and the Toolik Field Station. The Kuparuk River has its headwaters in the Brooks Range and drains through northern Alaska into the Arctic Ocean. Within these headwaters lies the Imnavait basin at an average elevation of 930 m. Water tracks run down the hill in parallel zones with a spacing of approximately 10 m. The Ridge Station was deployed at the end of Summer 2007.more » « less
-
This is the AmeriFlux Management Project (AMP) created FLUXNET-1F version of the carbon flux data for the site US-ICs Imnavait Creek Watershed Wet Sedge Tundra. This is the FLUXNET version of the carbon flux data for the site US-ICs Imnavait Creek Watershed Wet Sedge Tundra produced by applying the standard ONEFlux (1F) software. Site Description - The Imnavait Creek Watershed Wet Sedge Tundra (Fen Station) is located near Imnavait Creek in Alaska, north of the Brooks Range in the Kuparuk basin near Lake Toolik and the Toolik Field Station. The Kuparuk River has its headwaters in the Brooks Range and drains through northern Alaska into the Arctic Ocean. Within these headwaters lies the Imnavait basin at an average elevation of 930 m. Water tracks run down the hill in parallel zones with a spacing of approximately 10 m. The Fen Station was deployed at the end of Summer 2007.more » « less
An official website of the United States government
