Git Product home page Git Product logo

l2a-wind-direction-processor's People

Contributors

agrouaze avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

l2a-wind-direction-processor's Issues

the variable used for prediction is currently `sigma0` it should be `sigma0_filt`

If we look at

X = tiles_stacked_no_nan.sigma0.transpose("all_tiles", "azimuth", "range").values

we can see that sigma0 is used for the prediction.
In the meatime the Level-1B product evolved and introduced a sigma0_filt variable with (denoising and bright target correction) also it is NaN for the tiles with land while sigma0 in the latest version of the L1B product is always defined.
So I suggest to replace sigma0 by sigma0_filt.

handling tiles over land

We want:

  • all the subswath files generated in VV
  • all the L1B tiles present in the L2A file (could be filled with NaN if on land)
  • all the variables in the files even if on land.

simplify workflow/dataflow to get wind directions from SLC

currently:

  1. SLC ->XSARSLC xtiling-> L1B -> tiles corners
  2. SLC ->sigma0 calibrated+tiles corners (L1B) -> XSARSLC interface-> patches
  3. patches->L2A predictions->wdir

it could be more direct (all in L2A processor):

  1. SLC->xsarslc dependance->sigma0+tiles-> in memory patches->L2A predictions->wdir

what would be needed?

  • integrate interface.py in L2A wind dir processor
  • add xsarslc as optional dependency
  • skip production of patches
  • change the code to use L1B datatree in memory instead of the files

sphinx doc

  • notebook with predictions "pdf" and "regression" for product S1A_IW_XSP__1SDV_20210418T212223_20210418T212253_037510_046C42_6560.SAFE:IW1

clarify input Level-1B tiles size

default values for sigma0 patches in original network developed by @rmarquarlops are: 44x44 pixels.
These 44x44 pixels matrices are achieved using interface.py on a 17.6km² tiles at 400 m resolution in azimuth and range:

def get_low_res_tiles_from_L1BSLC(file_path, xspectra = 'intra', posting = {'sample':400,'line':400},
                                  tile_width = {'sample':17600.,'line':17600.}, window='GAUSSIAN', **kwargs):

but it seems that using Level-1B generated with a 17600m² size is leading to have sigma0 patches with NaN on the edges:

image
While we can get 44x44 sigma0 matrix starting from Level-1B produced on 17.7km² tiles without any NaN:
image

Question for @rmarquarlops : Should we start from Level-1B product with larger tiles (i.e. 17.7km² instead of 17.6km²)?
Having NaN in the sigma0 matrix does not prevent to do the prediction but the results are completely different compare to matrix without NaN.

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.