-
Notifications
You must be signed in to change notification settings - Fork 3
Workplan
ECMWF netCDF as Filesystem project
Fortnighty video meetings Weekly email updates FTP site for sharing netCDF sample files GitHub for code development - my intention is to use the Issue tracker feature for discussion.
First meeting this week - Start delayed slightly due to announcement delay from BeMyApp and then arranging the first meeting (I was on annual leave.) Agreed on practical issues for the project (Meeting times, sharing data and code (GitHub repo for code). ECMWF to provide a range of typical netCDF files used. Final software to be open source. Spreadsheet detailing annual leave to be set up.
Work on the proof-of-concept integrating fusepy and python-netcdf. (A basic implementation showing the two modules are compatible and can mount some basic form of netCDF data from an input file to a VFS.) Start of the documentation - will likely use Sphinx for this and initially host on the Github site or readthedocs.org.
Further time to enhance the functionality of the software, developing the types of netCDF data that can be mounted in the VFS, ideally progressing to basic image rendering of the variable data. (For gridded data).
Implementation of the core functionality of the software, i.e. mapping of netCDF Variables, Attributes, Dimensions etc. to logical positions within the virtual file system, and conversion to appropriate file formats (e.g. Text/Image/Binary). Completion of this milestone will consist the bulk of the development work. Feedback and discussion with ECMWF to facilitate changes to implementation details if necessary. This stage will be based on refining the initial proof-of-concept code developed in prior weeks.
Scoped time for continuing development of certain features of the software. (More details to be added here as project progresses and any issues identified that may require more time to implement or refine.)
Scoped time for continuing development of certain features of the software. (More details to be added here as project progresses and any issues identified that may require more time to implement or refine.) - Continued development of documentation.
Implementation of additional features, such as safety checking, optimisation if required, and netCDF compliance checking. Feedback from ECMWF and other interested users from alpha testing.
Final checking and testing of software, fixing of any outstanding bugs or requested changes. Time to develop user-guide and refine documentation for final delivery of software at end of August.
Further contingency time allowed to fix any outstanding bugs or issues raised.
Note: ESoWC website says 15th September end date (As well as 31st August?) (Either is fine for me unless there is a 'hard' deadline for either one.)