Weekly Status Report - 06/09 - 06/16

Activities:

• Read through various websites, documentation, etc, related to WRF 2.0 to try and gain a better understanding of the system’s expectations, limitations, etc
• Located a “namelist” description for WRF 2.0 online with descriptions of the various settings, which will be used in the project.  This list gives us each of the properties that will be adjusted as well as acceptable settings and descriptions of those settings.
• Discussed several items with Konstantinos, mainly involving the properties and functionality he needs for his experiments.
• Teams held a group meeting with Eric Johnson of FIU to discuss requirements/etc for the server which is now up and running.
• Compiled a list of JSP, SQL, etc, examples to use as references during the coding process.

 

Issues/Problems:

No technical issues last week, just physical ones.  I wound up with a bit of a stomach bug that put me out for a couple of days.  Luckily I was still able to get a fair bit of reading in.

One problem that is present, but I honestly feel is present in almost any project I’ve interacted with, is legacy.  If I have a question, I will often get six different answers if I asked it to six different people.  Everyone views the system a little differently with what they expect it to do and how they expect it to act.  In that regard, I think I should expect to need time at the end in which to preview the system to someone, perhaps Konstantinos, and make changes as is needed. 

Many different people have worked on this in the past while leaving very little notes/etc behind.  It is somewhat like trying to turn a short story into a novel—you know the basis, but your novel may not be exactly what the author had in mind.  It’s a goal of mine to make the information I find available to anyone who may follow after us, and I think Dr. Sadjadi’s request that we keep the Wiki updated will be a great way of doing this.

 

Plans:

Short-term:

• Get familiarized with the new server, accessing cvs, etc
• Begin working on the individual pages that will make up the website, starting with the properties page(s) so we can show this to Konstantinos early and give him time to request adaptations
• Meet and/or discuss with Selim the template through which the web portal and Job Flow Manager will interact

Long-term:

• Produce a 'dummy' version of the portal that will visually introduce all the functionality, but will not interact with the JFM just yet, and once completed begin adding functionality to it such as:
  • Interaction with the database
  • Sessioning
  • Uploading jobs
  • Downloading results
  • Sending/retrieving jobs between the portal and JFM
  • Capability to visualize the results