Aidan Heerdegen

I don't want to keep banging on, but with the approach I'm advocating in this issue an error such as https://github.com/COSIMA/master_index/pull/30 no longer stuffs up indexing for other experiments, as...

> I second @micaeljtoliveira calling it a ugly hack... ;-) I am feeling bullied :p

> In this case I would actually argue that the underlying problem lies with the indexing script, not the database. In my opinion the indexing script should not return an...

In case it isn't obvious, you could also include a DB update step to the [sync script](https://github.com/COSIMA/025deg_jra55_ryf/blob/master/sync_data.sh). Each experiment DB is then only updated when the contents of the directory...

Also can't fathom why I hadn't invoked this before 

> Another advantage of the database-per-experiment approach might be that people could use it more easily for their personal simulations (that they don't neccessarily plan to share with others). I...

> Will querying a database of databases slow down the explorer? My assumption was that it would speed it up, as I'm proposing the DBDB/Index would contain significantly less information...

> I would probably not go for a one database per experiment design as suggested by @aidanheerdegen :|

To be clear, are you saying this still works without the two extra lines ``` SST[‘xt_ocean’] = geolon_t[‘xt_ocean’].data SST[‘yt_ocean’] = geolon_t[‘yt_ocean’].data ``` with a 0.25 degree dataset?

Here are some examples of the four different `zoo` variables | id | path | |--|--| | 897 | `/g/data/ik11/outputs/access-om2/1deg_iamip2_his/output056/ocean/oceanbgc-3d-zoo-1-yearly-mean-y_2014.nc` | | 515 | `/g/data/ik11/outputs/access-om2/1deg_jra55_iaf_omip2_cycle5/output288/ocean/ocean_bgc_ann.nc` | | 698 | `/g/data/ik11/outputs/access-om2-025/025deg_jra55_ryf9091_bgc/restart050/ocean/csiro_bgc.res.nc`...