You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2015/04/09 20:05:12 UTC

[jira] [Closed] (AIRAVATA-1084) [GSoC] Prototype Airavata Support for Application Scheduling using Ultrscan usecase

     [ https://issues.apache.org/jira/browse/AIRAVATA-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru closed AIRAVATA-1084.
----------------------------------
    Resolution: Fixed

This GSOC project successfully concluded and is superseded by a GSOC 2015 project on benchmarking. 

> [GSoC] Prototype Airavata Support for Application Scheduling using Ultrscan usecase
> -----------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-1084
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1084
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Suresh Marru
>              Labels: gsoc2014, mentor
>
> Before a general purpose application specific monitoring could be built into Airavata Orchestrator, it will be good to prototype a one application specific monitoring and then think about how to generalize it. 
> As an example, Ultrascan application team Borries Demeler and Gary Gorbet were willing to provide a use case and access to information in their database to quert for the parameters that influence calculation time, such as number of datapoints, grid resolution, cluster hardware, noise fits, Monte Carlo iterations, etc. Based on these data, this prototype would do a multi-variate performance analysis and create a prediction model for the length of time it would take for a dataset to complete on a given resource. This will have to profile the 2 dimensional spectrum analysis (2DSA) and possibly Genetic Algorithm. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)