Git Product home page Git Product logo

Comments (8)

kandread avatar kandread commented on July 22, 2024

Severity is not PDSI, it's calculated from the empirical CDF of soil moisture as 100-Si where Si is the percentile relative to a climatology. Range of values is 0-100.

from rheas.

AdamJDuncan avatar AdamJDuncan commented on July 22, 2024

OK... sorry, what paper is this from? I don't really understand the "climatology" parameter here.

from rheas.

kandread avatar kandread commented on July 22, 2024

Climatology is the data used to build the CDF, the larger the sample the more accurate it will be. This paper contains more details http://journals.ametsoc.org/doi/abs/10.1175/JHM450.1

from rheas.

AdamJDuncan avatar AdamJDuncan commented on July 22, 2024

OK thanks I understand now. Definitely needs data back to '81, which I've been fetching since this morning (will test out SRI when that's done as using SQL in QGIS cancels all other operations... the clipped monthly SRI 1 & 3 maps for 2015/16 were sent to M for the mock-up late last night as the offending pixels weren't in the study area).

If the neighbourhood's 3x3 I guess the b-box needs to be extended 0.25 degrees on each side... are there any indices we'll be using which require a larger extension than that?

from rheas.

kandread avatar kandread commented on July 22, 2024

Not sure I understand the 3x3 neighborhood, are you referring to the severity calculation? That is done on a per-pixel basis so the bounding box shouldn't matter.

from rheas.

AdamJDuncan avatar AdamJDuncan commented on July 22, 2024

Areas of the LMR on the boundaries will affected by nodata in adjacent pixels during the spatial smoothing process, right? Would you say it's not enough to worry about?

This actually leads to related questions:

  1. Min threshold for clustering... is it 10 pixels, as per the paper? (If there's a drought in western Myanmar associated with Eastern India/Bangladesh but not the rest of the study area, it won't move on to subsequent calculations)
  2. Something I've been putting off... how important in your opinion is it to pull in the entire upstream basins of all rivers that flow into the region from the north? I'm assuming incoming runoff from higher elevations outside the study area is "0". Should we worry about basal discharge from the far reaches of the Mekong/Irawaddy/Salaween (essentially doubling the processing time), or would a few pixels -- accounting for groundflow that hasn't yet entered the stream network -- suffice?

from rheas.

AdamJDuncan avatar AdamJDuncan commented on July 22, 2024

(Sorry the question about clustering may seem a little obscure I think this is one of the most important outputs and I think that on the Servir/MRC end of things we should stop thinking of every output as being deliverable months from now... preparation for agronomic forecasting and crop yield calibration will take work, but there are in fact hydrological outputs that are actually close to deliverable now, and I want to get them right)

from rheas.

kandread avatar kandread commented on July 22, 2024

Severity calculations don't involve the spatial clustering approach described in the paper. That approach was used to identify drought events across space and time, given that pixels can go in and out of drought from month to month. The section of the paper that applies here is section 4 "Soil moisture and runoff percentiles" and that is calculated for each pixel independently.
Regarding your second question, if you're going to calculate streamflow (by running the VIC routing model) I'd say that they probably will have an impact. I'd calculate the contributing area upstream of your area's boundaries first and see how they compare to the drainage area at the basin outlets. If you're only focusing on runoff, including upstream pixels won't have any impact since VIC assumes that there's no horizontal transport of water at the macroscale.

from rheas.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.