Data Access Form

Dataset Title:	[Heat priming in Nematostella vectensis: Lethal temperature 50s (LT50s)] - Lethal temperature 50s (LT50s) displayed by larvae derived from dose-response curves after heat shock from experiments investigating heat priming in Nematostella vectensis (Influence of environmental pH variability and thermal sensitivity on the resilience of reef-building corals to acidification stress)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_923586_v1)
Information:	Summary \| License \| Metadata \| Background \| Files \| Make a graph

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable	Minimum	Maximum
Priming_temperature_C (degrees Celsius)	18	39
Group (unitless)	1	3
Days_post_fertilization (unitless)	4	11
LT50_C (degrees Celsius)	40.14	42.28

Server-side Functions

distinct()

Hover here to see a list of options. Click on an option to select it.

File type: (more information)

(Documentation / Bypass this form )

(Please be patient. It may take a while to get the data.)

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Priming_temperature_C {
    Int32 actual_range 18, 39;
    String long_name "Priming_temperature_c";
    String units "degrees Celsius";
  }
  Group {
    Int32 actual_range 1, 3;
    String long_name "Group";
    String units "unitless";
  }
  Days_post_fertilization {
    Int32 actual_range 4, 11;
    String long_name "Days_post_fertilization";
    String units "unitless";
  }
  LT50_C {
    Float32 actual_range 40.14, 42.28;
    String long_name "Lt50_c";
    String units "degrees Celsius";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.923586.1";
    String history 
"2024-11-08T05:51:31Z (local files)
2024-11-08T05:51:31Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_923586_v1.html";
    String infoUrl "https://www.bco-dmo.org/dataset/923586";
    String institution "BCO-DMO";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "(local files)";
    String summary 
"Across diverse taxa, sublethal exposure to abiotic stressors early in life can lead to benefits such as increased stress tolerance upon repeat exposure. This phenomenon, known as hormetic priming, is largely unexplored in early life stages of marine invertebrates, which are increasingly threatened by anthropogenic climate change. To investigate this phenomenon, larvae of the sea anemone and model marine invertebrate Nematostella vectensis were exposed to control (18 °C) or elevated (24 °C, 30 °C, 35 °C, or 39 °C) temperatures for 1 hour at 3 days post-fertilization (DPF), followed by return to control temperatures (18 °C). The animals were then assessed for growth, development, metabolic rates, and heat tolerance at 4, 7, and 11 DPF. To investigate a possible molecular mechanism for the observed changes in heat tolerance, the expression of heat shock protein 70 (HSP70) was quantified at 11 DPF. The study's findings suggest heat priming may augment the climate resilience of marine invertebrate early life stages via the modulation of key developmental and physiological phenotypes, while also affirming the need to limit further anthropogenic ocean warming.

This dataset includes data pertaining to the lethal temperature 50s (LT50s) displayed by larvae derived from DRCs after heat shock. See related datasets for other results from these experiments. These data and results are published in Glass et al. (2023) (DOI: 10.7717/peerj.16574).";
    String title "[Heat priming in Nematostella vectensis: Lethal temperature 50s (LT50s)] - Lethal temperature 50s (LT50s) displayed by larvae derived from dose-response curves after heat shock from experiments investigating heat priming in Nematostella vectensis (Influence of environmental pH variability and thermal sensitivity on the resilience of reef-building corals to acidification stress)";
  }
}

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its selection constraints (external link)

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.