2/18/2023 0 Comments Ioda training![]() ![]() ![]() ObsLocalization now has access to the GeometryIterator for the current gridpoint. ObsLocalization class was refactored to both find local observations, and compute the localization function. Here is JEDI-Algorithms summary for today's meeting: Now that cycl has been upgraded to python 3, this paves the way for a smooth implementation into ewok. Previous versions of cycl required python 2.7, which ewok is not equipped to handle. Yannick also announced that cycl has released a new pre-release. Ewok and R2D2 are otherwise ready for 4D, capably handling the large volume of data involved. Some of the filters throw exceptions when there are zero obs assigned to a particular MPI task. And they identified another problem with some of the filters at large partitions (many MPI tasks). They ran into a bug in how fv3 is reading namelists - this may or may not be specific to Orion. The team continues to make good progress in running, modifying and testing the 4D Hofx application with ewok on Orion. Guillaume and Andy were not present so then we moved on to JEDI I'll also be the acting lead for the OBS team in Dick's absence. New aerosol coefficient capability is available in v2.4.x, supporting other aerosol models (default is GOCART, we now support GOCART-GEOS-5, CMAQ, and NAAPS). It's being evaluated internally, and we expect a release with v2.4.1. We've made progress on the IASI-NG transmittance coefficients (TauCoef/SpcCoeff), which is the largest instrument (16923 channels) ever simulated by the CRTM team. This is intended to be the final v2.x release prior to the v3.0 development. We use the OSCAR satellite and instrument ID numbers internally to ensure consistency, perhaps this is one option.ĬRTM v2.4.1 is under development, it's a bug-fix release primarily, but does add additional openMP capabilities to thread over both channels and profiles, whereas v2.4.0 only had openMP over profiles. We can adopt the same naming convention for the CRTM coefficient files, loop me in on that specific discussion / assign me to the issues. Then Ben posted the following comment in the chat: Hui added that we should get input from stakeholders in setting these standards. Ryan and Greg agreed that this is a priority. ![]() JEDI1 session, and we plan on discussing our roadmap for BUFR then.Īfter his report, Yannick asked for a standardized list of instrument names as well as variables. The next general meeting will be on May 12, right before Mark's Solve their issues, we will move forward with prototyping how we can addĭue to an EMC time conflict, we are pushing the OBS3 meetings forward a Most of our radiance-based and conventional instruments. This work is necessary to ensure that we properly readĪll relevant data inside of a BUFR file, and EMC's current issue impacts Mnemonic sequences, and I have been told that task will take much longer ![]() NCEP's BUFR library to properly query variable-length, repetitive Currently, Ron McLaren is making significant enhancements to Goal, and we will use this to get rid of our dependency on GSI's ncdiagįiles. They are at the stage of generating test files for The goal is thatĭata transformations can occur in-memory and that we can directly queryĪn ODB data feed. Layer that we can incorporate as an engine in IODA. For ODB, AugustĪnd David Davies have made substantial progress in writing an interface Second, we want to bring ODB and BUFR data into IODA. With webpages that users can consult to understand our data layout. June, and around the end of Q1 we plan to publish a conventions document We want to standardize dimensions, units, and how we can tag data with Want inside of JEDI, and he focused on the variable names. Thompson has a working spreadsheet with many of the variables that we Now we want to go a bit further and implement variable conventions. Structure should they expect? Last year, we spent significant timeĪdding support for groups and multidimensional variables into IODA, and When a user accesses an ObsGroup in JEDI, what organizational Milestones coming up in the next two quarters, and we have a heavy focusįirst, we want to establish conventions regarding what makes valid IODAĭata. We did, let me mention some of what we plan on doing. Since it was the first meeting ofĪ new task and since we had several new JEDI contributors, much of theĭiscussion was about project logistics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |