Analysis of an established geocoronal H data set indicates a seasonal trend in observed dusk-to-dawn intensity variation, consistent with a diurnal variation in the underlying thermospheric hydrogen density. Observations were obtained at Pine Bluff Observatory, WI, from 2000 to 2001 using a high spectral resolution (R ∼80,000) Fabry-Perot annular summing spectrometer. This dusk-to-dawn asymmetry in intensity is highest in winter months with a difference of ∼2.7 Rayleighs and smallest in summer months with a difference of ∼0.5 Rayleighs; observations near equinox show a dusk-to-dawn difference in intensity close to ∼1.3 Rayleighs. Comparisons between modeled and observed dusk-to-dawn intensity variation show good agreement near the equinoxes. The modeled intensity was generated using the lyao_rt radiative transport code of Bishop (1999, https://doi.org/10.1016/S0022-4073(98)00031-4), employing NRLMSISE-00 thermospheric hydrogen profiles extended into the exosphere via the evaporative case of the Bishop analytic exosphere. Near the equinoxes and summer solstice, the model tends to agree with observations. Near the winter solstice, the model underestimates the dusk-to-dawn asymmetry by 1.5-2 Rayleighs. Overall, modeled H intensity generated with NRLMSISE-00 as the thermospheric input is shown to be consistently lower than observed intensity by a factor of ∼2.

No abstract

No abstract

The Geoscience Community Analysis Toolkit (GeoCAT) team develops and maintains data analysis and visualization tools on structured and unstructured grids for the geosciences community in the Scientific Python Ecosystem (SPE). In response to dealing with increasing geoscientific data sizes, GeoCAT prioritizes scalability, ensuring its implementations are scalable from personal laptops to HPC clusters. Another major goal of the GeoCAT team is to ensure community involvement throughout the whole project lifecycle, which is realized through an open development mindset by encouraging users and contributors to get involved in decision-making. With this model, we not only have our project stack open-sourced but also ensure most of the project assets that are directly related to the software development lifecycle are publicly accessible.