Status/Software/FREDWEB
From TeamFrednetWiki
| Group title: | FREDWEB group |
| Last report: | 2009-2-15 talk |
| Next report: | 2009-02-30 |
What work has your unit done since your last status report?
Thanks to a tip from Alan McNea, I were able to fix my computer's overheating problems to a great degree. Shortly after, however, I found a computer service shop with a good opening offer on fixing overheating issues (75% discount), so I sent it to repairs just to be sure (in some circumstances, like if processing for long periods of time, my computer would still shut off).
Also, we have upgraded FREDWEB from an unofficial 'side project' to the official mission control software prototype. This means that the team will use it to test out some mission control software concepts, with the approval of team management. If it works, there is a chance that it will be used for operations as well, but if not a different approach may be chosen for the final solution.
Furthermore, we are redefining FREDWEB from being strictly a data presentation solution, to support command and control as well. The way this is envisioned to be accomplished is in that it will support mission control web applications such as MCS Rover Director in addition to presentation-style applications. This will not be a significant change, since FREDWEB was already designed to be extensible, but we should rewrite the requirements to accommodate this change none-the-less.
I've also made some changes in the Mission Data API, specifically to the 'Resource Query' section. Since there is no way intrinsic way to signal if a long-lived request is wanted in HTTP, this section has been changed so it is now up to the server to define if a given URI resource is "pull" or "push" (long-lived). This also means that each parameter will normally be associated with two resources, instead of one: one for push and one for pull, where the latter is just a 'buffered' version of the former. If the URI of one of the two resources are known, the other can be looked up through the SPARQL interface.
Finally, work on the Mission Data Test Suite, which we will validate FREDWEB against, has begun, under the initiative of Yeonhoo Lee, and is making good progress. Yeonhoo has developed a basic RDF database demo with a toolkit known as 'RDF API for PHP' (RAP). We've set up a project page for the test suite on Launchpad, and set up Yeonhoo so he can commit to the Bazaar code branch on the Launchpad site as well. Yeonhoo's next step will be to implement end-point functionality (SPARQL protocol) in his demo. He misunderstood this task at first (confusingly, SPARQL means two different things), but we've now found that the RAP API has the functionality that we need, so he will just proceed with that.
How have your work and/or schedule deviated from the work planned at last report, if at all?
I pushed the report again due to too little to report, but every two weeks seems like a good frequency.
Also, the Mission Data API has not been made as explicit as hoped for in the last report, but I think it may be better to do this gradually in cooperation with Yeonhoo and his development of the Mission Data Test Suite, to get a practical impression of what works best.
What work do you plan to do before the next status report?
The User Interface API and Mission Data API will be made more explicit, such that coding, hopefully, soon can begin.
What information, if any, do you need from other groups or team members to do this work?
I will stay in touch with Yeonhoo about the development of the Mission Data Test Suite and the Mission Data API.
Also, I will discuss and coordinate the development of the User Interface API with Tobias Krieger who will effectively produce the first FREDWEB application, MCS Rover Director, soon.
What other work, if any, must be completed before you can do this work?
None.
What other resources such as equipment, infrastructure etc., if any, do you need to do this work?
I need my computer back from repairs. I expect it won't take too much more than another week.
We also need the IRC chat to stay online - it is proving very useful for collaborative debugging.
When do you think it would be appropriate to record the next status report for your unit?
On February 30, 2009.
Past reports
| Status/Software/FREDWEB/20090101 | Status/Software/FREDWEB/20090116 | Status/Software/FREDWEB/20090215 |
