1) Is the display itself rendered by your front end and you are just looking for back end API's to interact with the job? Or are you also looking for a way to develop a interactive front end using Airavata?
the preference is that the display is rendered by the backend. In other words it would be more like an X app. 2) Does the GPU cluster have a resource manager like PBS infront of it? Even better does it have any grid job managers like GRAM? our cluster has GPU and SGE - the GPU setting however is optional. For testing on Lonestar or Trestles we do not need the GPU function. 3) How interactive is the interactive use case? I mean do you need capabilities to stop, change re-run job like scenarios or is you looking to support remote OpenGL like capabilities? The concept is to interact with data - load data via the app and analyze it. The app has the ability to look at the local filesystem and select the data you want to analyze. Cheers, Suresh On May 14, 2012, at 5:58 PM, Joseph Hargitai wrote: > > Hi All, > > we are implementing a home-developed java tool that we: > > - want to run on a cluster > - have the data on the cluster > - have the display invoked from the gateway and passed back to the gateway > for user display/interaction > > what is the standard way to encapsulate such session in Airavata? > > the tool is unique in a sense that it is fully interactive but we prefer the > processing power of a backend for both GPUs and number of threads and memory. > > > best, > joe > >
