Note: We also seem to be pulling a few CI changes from @RobertPincus and the folks at the mother repo. Obviously this will not affect runs of GEOS. But it does probably mean our geos/develop is "out of sync" with the mother develop as they show a lot more changes on their develop compared to main. We'll most likely get those the next time we sync up with the mother repo (guessing at v1.7 time 😄 )
Also, I suppose we should look at submitting the sampled_urand_gen_max_ran routine if @dr0cloud thinks it should be passed upstream.
This adds the new
sampled_urand_gen_max_ranroutine used in https://github.com/GEOS-ESM/GEOSradiation_GridComp/pull/17 by @dr0cloud. We are merginggeos/developintogeos/mainso we can make a "geos" tag with the new routine.Note: We also seem to be pulling a few CI changes from @RobertPincus and the folks at the mother repo. Obviously this will not affect runs of GEOS. But it does probably mean our
geos/developis "out of sync" with the motherdevelopas they show a lot more changes on theirdevelopcompared tomain. We'll most likely get those the next time we sync up with the mother repo (guessing at v1.7 time 😄 )Also, I suppose we should look at submitting the
sampled_urand_gen_max_ranroutine if @dr0cloud thinks it should be passed upstream.