early days shiny app

[SnowpeaSoho]

It looks great!

•    Needs something to ensure exclusivity for variable name (exact match) e.g. sic will catch tsice inadvertently
  

•    Also something for version control since even if you specify all fields you will catch multiple versions of the same model output. Could strip dates out of version entry and have option to select latest (where specified)? Or else a check box (?) per table entry to select/deselect … or something. But some of it is weird too, like these both come up identically tabled for GFDL sic rcp85 OImon r1i1p1, the only differentiation is in the file path – are they duplicate outputs raijin has sourced from two sites?
  

/g/data/ua6/unofficial-ESG-replica/tmp/tree/cmip3.dkrz.de/thredds/fileServer/cmip5/output1/NOAA-GFDL/GFDL-CM3/rcp85/mon/seaIce/OImon/r1i1p1/v20110601/sic

/g/data/ua6/unofficial-ESG-replica/tmp/tree/esgdata.gfdl.noaa.gov/thredds/fileServer/gfdl_dataroot/NOAA-GFDL/GFDL-CM3/rcp85/mon/seaIce/OImon/r1i1p1/v20110601/sic

•    Early days yet I know but multiple variables to be selected and processed as a batch job?
  

Andrew L has a batch script (Ferret) he used to process sos and tos for some 16 models onto standard 1x1deg grids for a comparative analysis (obviously all the models have their own grids, #nodes etc). I wonder if redoing this procedure, and also processing PP and sic would be a good “test case” batch job to setup via R? I know you are interested also to setup processing for the various grids but this might be a useful alternative/interim step.

Sophie