Presentation is loading. Please wait.

Presentation is loading. Please wait.

Java Analysis Studio - Status CHEP 98 - September 1998 Tony Johnson - SLAC Jonas Gifford + Kevin Garwood - University of Victoria.

Similar presentations


Presentation on theme: "Java Analysis Studio - Status CHEP 98 - September 1998 Tony Johnson - SLAC Jonas Gifford + Kevin Garwood - University of Victoria."— Presentation transcript:

1

2 Java Analysis Studio - Status CHEP 98 - September 1998 Tony Johnson - SLAC Jonas Gifford + Kevin Garwood - University of Victoria

3 Contents b What is Java Analysis Studio b Java Analysis Studio Features b Implementation + Java Pro’s and Con’s b Beta Release Information b Demo b Future b Opportunities for Collaboration b Conclusion

4 What is Java Analysis Studio? b HEP Data Analysis Application b Easy to use + powerful GUI b Support Analysis Modules written in Java b Experiment and Data Format Independent b Supports n-tuple or Structured (object) Data b Data Location Independent (Local or Remote) b Extensible (via Plug-ins and Data Interface Modules (DIMS)) b Web + Internet compatible b Combination of custom and Commercial components (but no runtime license fees) b Based on Industry Standards

5 Java Analysis Studio Features b Rich, easy to use GUI

6 Java Analysis Studio Features b Data Format Independent Currently SupportCurrently Support –PAW n-tuples, Hippo n-tuples, any SQL database, flat-file n- tuples, StdHep MC events –Any data format via user supplied Data Interface Module (DIM) Experimenting withExperimenting with –Object databases (Objectstore, Objectivity) –Random access Java based IO (similar to root IO] FutureFuture –XML, Root, CDF/HDF

7 Java Analysis Studio Features b Supports both n-tuples and Structured Data n-tuples are fast and allow for simplifications in GUIn-tuples are fast and allow for simplifications in GUI – Simple Interactive cuts – Simple plot generation but n-tuples ultimately limiting Arbitrarily Structured Data provides ultimate flexibilityArbitrarily Structured Data provides ultimate flexibility –Requires slightly more work from end-user –Complete Object Oriented Analysis Environment –Flexible enough to write (or prototype) reconstruction code

8 Java Analysis Studio Features b Histogram/ScatterPlot Display Commercial plot package used in earlier versions replaced with custom plot packageCommercial plot package used in earlier versions replaced with custom plot package –Supports strings, dates, multiple axes, direct user interaction, overlays, fitting, scatter plots

9 Java Analysis Studio Features b User analysis modules written in Java Java Excellent Language for Physics AnalysisJava Excellent Language for Physics Analysis –Easy to learn yet very powerful, fully OO language –Fast (and getting faster] –Very fast code, load, test, fix cycle JAS provides built-in editor, compiler, plus:JAS provides built-in editor, compiler, plus: –hep.analysis package –for creating/filling/manipulating histograms –hep.physics package –simple particle, track manipulation package

10

11 hep.analysis package b Histogram delegates binning to: “partition classes” [idea stolen from LHC++ at last CHEP]“partition classes” [idea stolen from LHC++ at last CHEP] –Map from X, Y to bin number –supports real, integer, string, date’s etc. –Calculation of contents, errors in bin –allows efficiency plots, mean/rms plots etc –Data storage method –immediate binning (c.f. Hbook) –delayed binning, allows rebinning, axis changes via GUI Many standard partitions provided.Many standard partitions provided. User can provide own partition functionsUser can provide own partition functions

12 Java Analysis Studio Features b User Extensible, via Analysis ModulesAnalysis Modules Data Interface ModulesData Interface Modules –Access to experiment specific data, native language modules Plug In’s (c.f. Web Applets]Plug In’s (c.f. Web Applets] –Event Displays, etc. Fitter, Functions, PartitionsFitter, Functions, Partitions

13 Java Analysis Studio Features b Analyze local or remote data User interface independent of Data LocationUser interface independent of Data Location Does not assume fast network (works well at 28.8 bps]Does not assume fast network (works well at 28.8 bps] Analysis code moves (transparently) to dataAnalysis code moves (transparently) to data Desktop Client DIM Local Data Network Data Server DIM Remote Data

14 JAS Implementation b “100% Java” Application Uses Sun’s Java Foundation Classes (Swing) for GUIUses Sun’s Java Foundation Classes (Swing) for GUI [optional] interfaces to legacy data (PAW, hippo, StdHep) uses Java Native Interface [JNI][optional] interfaces to legacy data (PAW, hippo, StdHep) uses Java Native Interface [JNI] b Leverage Commercial Components Java itselfJava itself –compiler, GUI, debugger, networking, Remote Method Invocation Help system from OracleHelp system from Oracle Plot component (not currently used]Plot component (not currently used] Object databases, SQL databasesObject databases, SQL databases No runtime license feesNo runtime license fees

15 Java Pro’s and Con’s b Pro’s Very ProductiveVery Productive –No memory leaks –No subtle c++ problems –fun to write Cross Platform EasyCross Platform Easy –Develop under NT, –It just works elsewhere! Getting faster all the time:Getting faster all the time: –Swing 1.1 –Faster Java Virtual Machines –Hot-Spot Great tools availableGreat tools available –IDE’s –code optimizers –object modeling tools b Con’s Sun slow to fix bugsSun slow to fix bugs –printing –image handling No control over memory allocationNo control over memory allocation

16 Java Pro’s and Con’s b Is Java Fast Enough for HEP reconstruction??

17 1.0 Beta Release now available b Windows (NT, 95, 98] self extracting executable b Unix (Solaris+Linux) binary distribution available b Should be easy to port to other Unix, Mac etc. b Limitations Detailed documentation still under developmentDetailed documentation still under development May still be some changes to user APIMay still be some changes to user API b Download from: http://www-sldnt.slac.stanford.edu/jashttp://www-sldnt.slac.stanford.edu/jas

18 Demo

19 Future b More Data Interface Modules b More types of plots (lego plots etc.) b Built in debugger, code profiler b More n-tuple handling tools (c.f. HippoDraw]

20 Collaboration b Integrate Wired event display as “Plug In” b Working with FLCD, Babar b Looking for collaborators on hep.analysishep.analysis hep.physics packages (c.f. CLHEP)hep.physics packages (c.f. CLHEP) b Looking for other experiments interested in trying Java Analysis Studio out

21 Conclusions b Please try it: http://www-sldnt.slac.stanford.edu/jashttp://www-sldnt.slac.stanford.edu/jas b Please give us feedback jas-feedback@sld-mail.slac.stanford.edujas-feedback@sld-mail.slac.stanford.edu b Mailing List: http://www.slac.stanford.edu/cgi-bin/lwgate/JAS-L/http://www.slac.stanford.edu/cgi-bin/lwgate/JAS-L/ b Also general mailing list for Java in HEP: http://www.slac.stanford.edu/cgi-bin/lwgate/HEP-JAVA/http://www.slac.stanford.edu/cgi-bin/lwgate/HEP-JAVA/


Download ppt "Java Analysis Studio - Status CHEP 98 - September 1998 Tony Johnson - SLAC Jonas Gifford + Kevin Garwood - University of Victoria."

Similar presentations


Ads by Google