Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3DC8C465 for ; Thu, 11 Dec 2014 14:16:07 +0000 (UTC) Received: (qmail 15416 invoked by uid 500); 11 Dec 2014 14:16:07 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 15368 invoked by uid 500); 11 Dec 2014 14:16:07 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 15358 invoked by uid 99); 11 Dec 2014 14:16:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Dec 2014 14:16:06 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of spamidig@illinois.edu designates 192.17.82.70 as permitted sender) Received: from [192.17.82.70] (HELO pps03.cites.illinois.edu) (192.17.82.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Dec 2014 14:16:00 +0000 Received: from citesht3.cites.illinois.edu (citesht3.cites.illinois.edu [128.174.34.208]) by pps03.cites.illinois.edu (8.14.5/8.14.5) with ESMTP id sBBEBL6N002664 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 11 Dec 2014 08:13:35 -0600 Received: from CITESMBX1.ad.uillinois.edu ([169.254.3.179]) by CITESHT3.ad.uillinois.edu ([128.174.34.208]) with mapi id 14.03.0210.002; Thu, 11 Dec 2014 08:12:42 -0600 From: "Pamidighantam, Sudhakar V" To: "dev@airavata.apache.org" CC: Srinath Perera , Dilum Bandara Subject: Re: DataCat Project Progress Thread-Topic: DataCat Project Progress Thread-Index: AQHQFSsKsuHgqvzFqE6SSq7pSaX6RZyK00uA Date: Thu, 11 Dec 2014 14:12:41 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.174.34.198] Content-Type: multipart/alternative; boundary="_000_DBE83381C3C54E7EAA8763A723AFCBC3illinoisedu_" MIME-Version: 1.0 X-Spam-Score: 0 X-Spam-Details: rule=cautious_plus_nq_notspam policy=cautious_plus_nq score=0 kscore.is_bulkscore=3.36841665671272e-13 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.221612580512166 urlsuspect_oldscore=0.221612580512166 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=0 rbsscore=0.221612580512166 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1412110141 X-Spam-OrigSender: spamidig@illinois.edu X-Spam-Bar: X-Virus-Checked: Checked by ClamAV on apache.org --_000_DBE83381C3C54E7EAA8763A723AFCBC3illinoisedu_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Supun: I support these goals. I am available for you to engage with you and anythi= ng I can do to expedite the project please let me know. Even if you think I= can not, do please ask anyway. I have written the original parsers in perl myself and have directed others= when the Cup/JFLex system was put in place. I have generated and modified = the CUP/JFlex code before, so I am familiar with how it works. I will look = at the paper and may suggest additions. I can not test the system now by adding more data and see if this can parse= the new data. How can we get to that point. This is critical first step fo= r me before I can ask friendly users to test this further. Current state is= a prototype only and is not interesting enough for any of our users. Unles= s we can add parsing of more data and more salient data and create products= it is difficult engage end users in any meaningful way. Perhaps if this is deployed somewhere in Indiana it may be easier to move f= orward. If you need more data please let me know where I should locate it f= or you to access. Thanks, Sudhakar. On Dec 11, 2014, at 4:11 AM, Supun Nakandala > wrote: Hi All, We had the mid evaluation of the project last Tuesday and the following con= cerns were raised. 1. The lack of visibility of the overall solution in the project demonst= ration. 2. The ability to come up with a solution where, scientist who does not = have a background in computer science can create new parsers (metadata extr= action logic) The project was demonstrated using the web interface that we developed. For= the final evaluation we expect to demonstrate the system using laravel PHP= Reference Gateway running in a production server and demonstrate how a new= data product that gets generated will be identified, indexed and will be a= vailable for searching and hope this will handle the first issue. We also had a meeting with Dr. Dilum our internal supervisor where we ident= ified things that can be done from now to 15th January, the expected projec= t completion date 1. Do a proper performance test and publish a paper before final marks f= or the project is finalized (marks will be finalized by the end of March). 2. Getting to work more parsers, so that Sudhakar can ask more users to = use the system. This will help to get more feedback on the system and have = a real world usage. 3. Implement the support for provenance aware workflow execution in Aira= vata using our system. We have written a draft paper which I have attached here with. We showed th= is to Dr. Srinath and Dr Dilum and they suggested that we do a proper perfo= rmance testing (The one that already done is not up to the expected standar= ds). Given the available time we need to prioritize our work and select a s= et of tasks that is doable and has the most impact. What do you all think? Draft Paper: https://docs.google.com/document/d/1PLfST6hLygQpsr4RlgiDoffmDE= wMOWbmb1WZ0uKTtd8/edit#heading=3Dh.6fjqfavj2nov Literature Review: https://drive.google.com/file/d/0B0cLF-CLa59oaXRBazF1aUR= vQTg/view?usp=3Dsharing Supun --_000_DBE83381C3C54E7EAA8763A723AFCBC3illinoisedu_ Content-Type: text/html; charset="us-ascii" Content-ID: <7E598C842B5CF44EB758C4D9AD1C5339@mx.uillinois.edu> Content-Transfer-Encoding: quoted-printable Supun:
I support these goals. I am available for you to engage with you and a= nything I can do to expedite the project please let me know. Even if you th= ink I can not,  do please ask anyway. 
I have written the original parsers in perl myself and have directed o= thers when the Cup/JFLex system was put in place. I have generated and modi= fied the CUP/JFlex code before, so I am familiar with how it works. I will = look at the paper and may suggest  additions. 

I can not test the system now by adding more data and see if this can = parse the new data. How can we get to that point. This is critical first st= ep for me before I can ask friendly users to test this further. Current sta= te is a prototype only and is not interesting enough for any of our users. Unless we can add parsing of more= data and more salient data and create products it is difficult engage end = users in any meaningful way. 

Perhaps if this is deployed somewhere in Indiana it may be easier to m= ove forward. If you need more data please let me know where I should locate= it for you to access.

Thanks,
Sudhakar.


On Dec 11, 2014, at 4:11 AM, Supun Nakandala <supun.nakandala@gmail.com> wrote:

Hi All,

We had the mid evaluation of the project las= t Tuesday and the following concerns were raised.
  1. The lack of visibility of the overall solution in the project demonstra= tion.
  2. The ability to come up with a solution where, scientist who d= oes not have a background in computer science can create new parsers (metad= ata extraction logic)
The project was demonstrated using the web interface that we developed= . For the final evaluation we expect to demonstrate the system using larave= l PHP Reference Gateway running in a production server and demonstrate how = a new data product that gets generated will be identified, indexed and will be available for searching and hope t= his will handle the first issue.

We also had a meeting with Dr. Dilum our internal supervisor where we = identified things that can be done from now to 15th January, the expected p= roject completion date
  1. Do a proper performance test and publish a paper before final marks for= the project is finalized (marks will be finalized by the end of March).
  2. Getting to work more parsers, so that Sudhakar can ask more users to = use the system. This will help to get more feedback on the system and have = a real world usage.
  3. Implement the support for provenance aware work= flow execution in Airavata using our system.
We have written a draft paper which I have attached here with. We show= ed this to Dr. Srinath and Dr Dilum and they suggested that we do a proper = performance testing (The one that already done is not up to the expected st= andards). Given the available time we need to prioritize our work and select a set of tasks that is doable an= d has the most impact. What do you all think?



Supun

--_000_DBE83381C3C54E7EAA8763A723AFCBC3illinoisedu_--