You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
Agenda
| Who | Plan for the week (Monday) | Accomplished (Friday) |
|---|
| - Package python code and change dependencies accordingly
| |
| | |
| Development: -
NDS-412
-
Getting issue details...
STATUS
-
NDS-387
-
Getting issue details...
STATUS
-
NDS-390
-
Getting issue details...
STATUS
-
NDS-398
-
Getting issue details...
STATUS
-
NDS-397
-
Getting issue details...
STATUS
Next week (or this week if there's time): -
NDS-399
-
Getting issue details...
STATUS
-
NDS-366
-
Getting issue details...
STATUS
| Development: -
NDS-412
-
Getting issue details...
STATUS
-
NDS-390
-
Getting issue details...
STATUS
-
NDS-398
-
Getting issue details...
STATUS
-
NDS-397
-
Getting issue details...
STATUS
-
NDS-387
-
Getting issue details...
STATUS
Review: -
NDS-374
-
Getting issue details...
STATUS
Still working on: -
NDS-325
-
Getting issue details...
STATUS
-
NDS-366
-
Getting issue details...
STATUS
|
| - Blue Waters workshop
- CC* proposals
- DIBBs/Datanet position paper
| - Blue Waters workshop
- CC* proposals (coming together)
- Revised DIBBs/DataNet position paper and sent back
- Distributed NDSC draft report to TAC
|
| - script for parsing log files
- continue description of AFM format ibw with Todd
- templates with MDF description, data ingestion, screenshots
- meet with prof. Jasiuk's student, insert data
| |
| - PSi
- test large messaging - They wish to send up to 50MB messages, unclear how well this might work
- develop an example using messagepack for packing data structures over channels
- define and prototype integration with kacpers suggestions for workflow, data management, and jupyter - clarify who's doing what
- NDS
-
NDS-395
-
Getting issue details...
STATUS
NDS-295
-
Getting issue details...
STATUS
NDS-346
-
Getting issue details...
STATUS
NDS-343
-
Getting issue details...
STATUS
| |
| | |
| | |