Development Notes

[qjhart]

Development

DWR development and testing machines

Development at UC Davis

UC Davis is a bit more loose with their processing, due to the lesser number of machines. Development at UCD is down by different users testing their code on a different GDB location, with test data copied over.

Users can also develop the steps to get data the processor, by creating their own incrontab functions to replicate the cimis user incrontab.

Branching and Merge Requests

There are two continuous branches master and dev. The master branch is considered to be the production version of the latest implementation of the production ready code for the GOES Spatial CIMIS processing. The production servers at DWR should only ever run the master branch.

The dev branch is the development branch, that is always run on the DWR test machine, and sometimes run on the development machine. The dev branch is considered to be the next master. you should never commit to dev a half-completed fix. We strive to keep dev operational.

Other branches in the project are development components that are being worked on. Every development issue that can be separated from other issues, should be developed in it's own branch. When they are complete, they these branches are then merged into dev.

After merge, the other branches can be deleted. When the master branch is a a new revision, that the master branch is Tagged with that revision.

GOES15

• GOES-15-last-gvar This was the last component of the master branch that used the GOES-15 GVAR stream as input. There is a tag on the master branch pointing to this location.

• Subsequent revisions of the master branch use the GOES-16/17 processing setup. This includes changes in how the data is stored on the receiver, how it's pushed to the processor, and how the processor manages the data.

[qjhart]

2019-04-25 Sprint meeting

• Sean Terry is planning to come out later in the year (mid-late june), for a time that will coincide with CSTARS moving their data to GOES-17. Sean will direct DWR on the installation of the new noise filters, and does not need to come out for that.

• Sav indicated that the new production machine was ready, the volumes were currently being tested.

• Quinn discussed the plan for moving GOES-15 data directly to production machines, and the total size required for the GOES-15 data plant (~500G)

Git hub Issues

• DWR Monitoring, Alerting and Issue Resolution Strategy #48 George needs to work w/ DWR on shared monitoring scheme
• Formulate a plan for transfer of the old DWR data to the new system #33 Based on Sav's note, transfers to test and dev will go via the windows machines.

Decisions

• GITHUB is sprint tracking tool

TODO

• DWR will make an ISSUE for DTS transfer
• DWR will review the Development Notes Development Notes #44
• Brett / Sav Install github on windows Install GIT tools onto windows Machines #50
• DWR make production machine available Access to the production system #53