tbep-tech / temp-manu Goto Github PK
View Code? Open in Web Editor NEWMaterials for the manuscript describing temperature trends in Tampa Bay
Materials for the manuscript describing temperature trends in Tampa Bay
Line 173 in 74a1b19
avg annual rainfall hasn't really changed over the period of record tho, no? it is a bit misleading to reference 1975 as a baseline since it was a significant drought (see usgs records, https://pubs.usgs.gov/wri/1978/0029/report.pdf for example)
Another distinction of the FIM data/models are that the depths of the samples are compatible with seagrass growth.
Line 221 in 2f8e57c
Consider using more distinct colors for top and bottom measurements https://github.com/tbep-tech/temp-manu/blob/main/figs/meteowqraw.png
Line 79 in 74a1b19
was our hypothesis really that tampa bay was getting fresher? or was that informed by preliminary analysis? it seems like the conventional wisdom of local managers is that the bay would be saltier and some lit reviews concur that a local expression of slr trends saltier, despite global salinity trending fresher (given ice melt, etc. ) see https://doi.org/10.1016/j.ocecoaman.2023.106490
i like that the conclusion notes that this finding is somewhat surprising and wonder if there might be a benefit from reframing the hypothesis here.
Throughout the manuscript, changing "physical" conditions due to climate change are referenced. Since we're using temperature and salinity as metrics "physicochemical" conditions might be more appropriate.
Consider using a transformation on the FIM % cover data especially considering the high number of zeros. I've used log(x+1) in previous data analyses. https://github.com/tbep-tech/temp-manu/blob/main/figs/sgmods.png
Change the red points in panel a to black to avoid red/green issues
https://github.com/tbep-tech/temp-manu/blob/main/figs/map.png
The hypersaline conditions in Florida Bay are likely not due to just drought; evapotranspiration and wave-driven circulation are major drivers in the hydrologically distinct basins of FB, and lack of effective restoration of freshwater sheet flow (as of yet) into the north central region of the bay complicate the issue. Suggest deleting the first part of that sentence - the point is still made without mentioning drought. Hypersalinity may continue to be a chronic issue there regardless of rainfall/freshwater flow.
Line 231 in 2f8e57c
Maybe say "shallow" or <1.5 m, because some sites are offshore as long as the depth is amenable to seining.
Reference dataset used for these figures in the figure legend - EPC, correct?
https://github.com/tbep-tech/temp-manu/blob/main/figs/mixeff.png
Also reference dataset used in text here to keep everything straight:
Line 193 in 2f8e57c
Top and bottom temperatures were used from EPC data in Figure meteowqraw, but the rest of the analyses were completed on bottom temperatures, correct? In the FIM data section, it states that only bottom measurements were used, but is that also true for PDEM data? That needs to be explicitly added in the methods for PDEM somewhere and probably in each figure legend and the equations for clarity.
https://github.com/tbep-tech/temp-manu/blob/main/figs/kendall.png
My first thought is to constrict the seagrass analyses to the FIM data since all data are collected at the same station and the depths are all suitable for seagrass growth; it will simplify the message, plus the inconclusive results of the EPC and Pinellas Co. models don't make a compelling reason to keep them. The SWFWMD seagrass cover and transect data would still be used to demonstrate seagrass change over time.
The analyses for light attenuation address the reviewer's comments but don't really add anything to the story (especially for the FIM data), so I suggest leaving those as responses to comments rather than including them in the revised manuscript. The reviewers seemed to be most concerned about statements that light availability (as well as nitrogen, chlorophyll a) was relatively constant, Maybe simple graphs by year, dataset, and bay segment (without incorporating the seagrass data) to account for temporal differences in these factors would suffice?
I see what you're getting at with the "heat map" graphs of partial effects by month and stressor, but it took me awhile to decipher it. Is there a simpler way to display these data? If kept, change the y axis labels to 2,5,7, etc. so that it's clear that it's by month.
From the discussion, "The unique combination of very dense T. testudinum and sustained, 15 yr high salinities coincident with elevated and increasing summertime water temperatures may have resulted in a tipping point that exceeded the physiological tolerances of this species." Figure 3 has a time series of bottom water salinity and temperature from long term monitoring stations.
Possibly add a sentence to the paragraph on regional seagrass loss patterns? Another example of recent seagrass loss in Florida Bay may be attributed to increased summer temperatures (in some cases >38 C) and sustained high salinity (50-60 ppt for multi-week periods). In this case, higher salinity may be the more important stressor, demonstrating a different pattern than we see in TB.
"All of the organizations that provided water quality datasets participate in the Southwest Florida Regional Ambient Monitoring Program [@sherwood2016]." FIM does not participate in this, and from my understanding the split samples are for laboratory results, not in situ water monitoring for temperature and salinity.
Line 225 in 74a1b19
Suggestion: Hot and fresh: evidence of climate-related suboptimal conditions for seagrass in a large Gulf coast estuary
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.