LOC Meeting tomorrow (10/26 at 4PM EDT). Dave Neufeld is not able to attend so Gordon contacted Mark Wolfire. Mark will also not be able to attend so Gordon has contacted Michael Kaufmann. Still waiting for a reply.
Tutorial registration is now open and the "mass email" was sent out today. We still are trying for a limit of 60 people and currently there are 44 people registered for the tutorial which include a handful of trainers. We may be able to expand it if the need arises.
PRIMER - it is now time to send the ES PRIMER to the other ARCs for review and comments. However, we need to impose a deadline on the ARCs for incorporating edits. This should be done ASAP as we prepare the final version for the AAS/Victoria meetings.
Kartik not online for this meeting
Update on Train The Trainers
Rachel reported that she has insufficient information as to exactly what is expected of the trainers.
ACTION ITEM: KS to send more specific information to the trainers.
Kartik sent around homework for all TTT participants. Jim wanted to know about the right version of the OT to download and install.
ACTION ITEM: Jim will follow-up with Harvey on the latest most stable version of the OT to install. One that will work on our version of Linux in CHV is preferred. He will report back to us on the progress.
There is wiki that is expected to be set up for problems like which version of the OT to install.
ACTION ITEM: KS to followup on that wiki and include the OT problem.
Visitors will be able to use room 211 for the TTT session. This can accomodate 6-8 people.
There is wiki page set up that holds all the old presentations but gets rid of the ones that are outdated or convey the wrong information per Carol's suggestion. See below:
Is this our responsibility? - for the NA community, yes
Does the OT user manual address these concerns? - NO
The OT manual describes the software - it is not helpful in preparing or submitting a proposal.
So what do we (ie, the NAASC) need in terms of documentation? Taking an overview of all that's needed without considering what already exists, or is planned, in one form or another, Jim came up with the following broad categories of required documentation.
Why should the user be interested in ALMA? - Taken care of by the PRIMER
Proposers Guide - (in preparation and should be less than 10 pages) See below:
ACTION ITEM: Jim will work on preparing the Proposer's Guide with the intention that it will be released after the CfP. In addition, he will coordinate with John in organizing this effort because there were a lot of "Plans for Early Science" documents prepared by the ARCs for the reviews.
How does the Proposer's Guide overlap with the NAASC Users Guide?
The NAASC guide should present what the NAASC does and provides to the community.
ACTION ITEM: Jim, Aaron and Scott to review overlaps of material between the web and documents such as the proposed proposer's guide, and define what the "user's guide" should be (document; new web pages; woven into existing web).
Science Web (Aaron)
No update this week. There is still discussion on how to get the NRC logo onto the NAASC page.
Victoria has updated their pages and have provided Aaron with the appropriate links.
Work over the last week has been focused on the deployment of the helpdesk scheduled for early/mid Dec. The deployment of the helpdesk is dependent on the rollout of the ALMA User Portal. If that is not ready by mid/Dec, we still have the NAASC department available for questions through the NRAO helpdesk. However, those tickets will not be mirrored to the other ARCs.
In addition to setting up the helpdesk, there has been a lot of discussion on reporting to make sure any one USS is not overwhelmed with tickets.
Remijan and Sharp have looked at the canned reports available through Kayako and decided they are not adequate for any type of reporting, especially to the other ARCs.
ACTION ITEM: Remijan and Sharp are preparing a short presentation that will be made available to the other ARCs on what type of reporting that can be generated using mysql queries from the Kayako database.