flowchart TD A0([Início<br/>Modo Automático FFT]) A0 --> B1[Capturar N amostras<br/>(buffer de áudio)] B1 --> B2[Aplicar janela de ponderação<br/>(ex.: Hann)] B2 --> C1[Calcular FFT] C1 --> C2[Encontrar bin de maior magnitude] C2 --> C3[Calcular<br/>freqDominante = k·Fs/N] C3 --> D1[Definir low-cut = freqDom – 100 Hz] C3 --> D2[Definir high-cut = freqDom + 100 Hz] D1 & D2 --> E1[Atualizar sliders<br/>(low-cut & high-cut)]

iSamples Property Graph in Parquet This document describes the parquet representation of iSamples material sample records. The basic pattern is that rows in the parquet file represent nodes and edges. Each node entry corresponds with an instance of a class in the iSamples model. Columns are the union of columns across all the objects. The iSamples parquet files are structured with a metadata section (stored in the parquet key-value metadata section), and the data section: KV Metadata pqg_version pqg_primary_key

This page: https://bit.ly/dv20240531 Slides Cesium Zenodo DOI: https://doi.org/10.5281/zenodo.11400484 Hopper STAC-browser STAC samples Static iSamples

Sample Reliquary Draft This document contains draft information on development of sample reliquary support in the iSamples project. Summary reliquary _noun a container or shrine in which sacred relics are kept A sample reliquary is a mechanism to reference a set of samples. Sample references are achieved through the use of persistent, resolvable, globally unique identifiers.

--- title: Example Git diagram --- gitGraph commit commit branch develop checkout develop commit commit

{ "@type": "PhysicalSampleRecord", "sample_identifier":"", "alternate_identifiers":[{ "@type": "IdentifierObjct", "label": "", "identifier": "", "scheme_name": "" }], "complies_with":[""],

Vocabularies in iSamples are used to provide discrete labels that help to categorize samples. The vocabularies are generally hierarchical in nature with a top level broad concept and progressively narrower concepts. Relationship between the concepts are defined using the Simple Knowledge Organization System (SKOS) common data model. Herein skos refers to http://www.w3.org/2004/02/skos/core# A vocabulary as used in iSamples is an RDF graph composed of one instance of skos:ConceptScheme and one or more instances of skos:Concept. One or more of the skos:Concept instances should include a skos:topConceptOf predicate, the object of which is the skos:ConceptScheme for the vocabulary. If a skos:Concept does not include a skos:topConceptOf predicate, then it should contain a skos:inScheme predicate that refers to the skos:ConceptScheme instance.[^a] A skos:Concept instance that does not include a skos:topConceptOf predicate must include a skos:broader predicate, the object of which is an instance of skos:Concept with a broader definition.

%%{init: {'securityLevel': 'loose', 'theme':'neutral', 'themeVariables': { 'fontSize':'14px', 'fontFamily':'Roboto Mono'}}}%% classDiagram direction RL class PhysicalSampleRecord { alternate_identifiers : IdentifierObject[] complies_with : string[] curation : SpecimenCuration description : string has_context_category : IdentifierObject[] has_material_category : IdentifierObject[]

SESAR Transition to iSB Goal Migrate SESAR from current PHP deployment to use iSamples-In-A-Box (iSB) with no loss of capability. Process Connect iSB to SESAR Postgres database.Transformer to generate iSamples core records from SESAR database records. Persist transformed records to database. Triggers to update transformed records on change to sources. Update iSB to use SESAR database

Field Sample Identification Problem : Associating a globally unique, resolvable, persistent, identifier (GURPI) to a physical sample collected in the field with limited connectivity and technical capacity. There are basically three approaches to ensuring uniqueness of generated identifiers: Algorithmic global uniqueness Selection from a predefined list Context dependent uniqueness

When: Fridays, 12:00 ET Where: https://arizona.zoom.us/j/84283310669 Notes: https://hackmd.io/SLE_8TwcSJu5fTeqwkdXng These notes are stored in github under home/notes/tech_notes.md. Notes from earlier meetings are at https://docs.google.com/document/d/1GIScduypIrdPi5P62DhvrBCmCw0ypkEJpAM8iQNzCkw/edit?usp=sharing 2023-03-24 2022-07-22 2022-05-20

See also: https://github.com/isamplesorg/isamples_inabox/issues/198 iSB-Lite There is a need for a simple system to support field data collection in an offline-first system that enables content creation and editing with no Internet connection, but is able to seamlessly participate in the iSamples network when a network connection becomes available. This experiment will leverage CSV for file storage, git for revision control, GitHub for serving static content, and if necessary, supporting services operating within the constraints of zero-cost hosting such as on Deta, Vercel, Google App Engine, or AWS. Workflow Basic workflow:

General notes on Identifiers An identifier is a sequence of characters used to identify a resource. A resolvable identifier is an identifier which, when provided to a resolving service, provides the location of the identified resource. There are many implementations of resolver services, most mated to particular types of identifier, or identifiers that conform to a particular scheme. Each identifier scheme defines syntax and behavior peculiar to the scheme. However, there are elements of common syntax and behavior across the common successful schemes. This document attempts to describe the common syntax and behavior, with particular emphasis on DOI, IGSN, and ARK identifiers within the broad context of the earth, environmental, and biological sciences. Syntax Identifiers generally have several components: $$ \color{navy}{\mathtt{Scheme}}:\color{salmon}{\mathtt{Prefix}}/\color{red}{\mathtt{Shoulder}}\color{darkorange}{\mathtt{Suffix}}\color{lightblue}{\mathtt{Extra}}

Identifier minting Minting identifiers is the process of creating a new identifier and associating it with some resource. Workflow for iSamples identifier minting support. In this case, iSB is acting as an allocating agent for a researcher. The metadata associated with the sample is only persisted with DataCite and the Researcher: actor Researcher participant iSB participant ORCID participant DataCite == Authentication ==

digraph G { rankdir="BT" M [label="Material"] NSM [label="Natural\nSolid Material"] Fl [label="Fluid Material"] Mi [label="Mineral"] Mi -> NSM [label="Broader"] NSM -> M [label="Broader"] Fl -> M [label="Broader"] more [label="...", shape=none]

Upgrading python3 on mars apt list --installed | grep python3.9 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libpython3.9/bionic,now 3.9.12-1+bionic2 amd64 [installed,automatic] libpython3.9-dev/bionic,now 3.9.12-1+bionic2 amd64 [installed,automatic] libpython3.9-minimal/now 3.9.12-1+bionic1 amd64 [installed,upgradable to: 3.9.12-1+bionic2] libpython3.9-stdlib/now 3.9.12-1+bionic1 amd64 [installed,upgradable to: 3.9.12-1+bionic2]

iSamples: A distributed system facilitating access to information about physical samples gathered primarily from the natural environment. Resolvable, unique identifiers are essential Collection instances ("iSamples in a box", iSB) hold content iSamples Central aggregates common view Flexible topology iSamples Context !include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Container.puml

Frictionless Source Data The standard mode of operations for iSamples is to first retrieve a list of resources (advertised using sitemaps), then retrieve the advertised resources using the locations provided in the sitemaps. object "Source A" as catalogA object "iSB A" as iSBa catalogA ..> iSBa object "Source B" as catalogB object "iSB B" as iSBb catalogB ..> iSBb

iSamples Context !include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Container.puml System(isc, "iSC", "iSamples Central") System_Boundary(isamples, "iSamples"){ System(isb, "iSB", "iSamples-In-A-Box") System_Ext(collection, "Collection", "Collection of sample records") Rel(isb, collection, "Get records from collection") }

iSamples Architecture Notes 2021-09-24 Notes on the overall design and deployment of iSamples https://hackmd.io/@isamples/BkWlLDo7K#/ !include https://raw.githubusercontent.com/datadavev/C4-PlantUML/master/C4_Component.puml