Validation Tasks

This pages lists the tasks for the Geant 4 Validation Task Force

Data Base related tasks:

1. clean up current database (done, Hans)
2. evaluate if G4 validation and DRImageDB can use the same schema and if the two development efforts can be merged (just using different configurations)
3. set up production database (install schema and data) (done, Hans )
4. use the development database (which we are currently using) as development database (done)
5. setup db connection pool on glassfish web application server-->that will make our own connection pool library obsolete, and will simplify start up ...(unfortunately that doesn't work since glassfish returns a connection pool that doesn't support all the postgresql database extensions we are using (e.g. handling of blobs), We updated the current code to use JDBC4 connection pool, done)
6. setting up second web application server to be able to do development (done Hans)
7. document the installation and set up of web application server.(done Hans)
8. extend database schema, to be able to store and display histogram data and experimental data. Currently we are investigating the best way to store this experimental data in the db (prototype in place) .
9. populate the database with the experimental data that's currently used for tests (done for test 48)
10. import more data when it becomes available (ongoing tasks will be replaced by automation nearly done) .

Web-application related tasks:

1. web-application needs to be able to retrieve and display histogram data and experimental data. A Plotting tool like JFreeChart seems like a good application. (prototype in place)
2. Currently the way that the menus are created in the web-application needs to be rewritten. Currently the html file that is passed is much too big and we should only create the selected menus from the database on the fly.
3. need to update the java library that provides the connection to the database to provide more functionality (e.g. more search functions)
4. new security model originally developed on tomcat server but since we are now using glassfish we have to get this working again. (currently we are using the security model provided by the glassfish web application server, so all the services that required authentication have been restored)
5. implement role based access to various functions.
6. list all tests and descriptions on home page, currently this is only available on expert pages.
7. provide nice introduction on home page
8. provide release highlight age.(done Julia)
9. update G4ValidationLib to use JDBC4 (done)
10. extend G4ValidationLib to support experimental data and histogram data which are already supported by the data base.
11. implement filtered access to the data (e.g. public, G4Experts etc. will have access to various subsets of tests. E.g. the public doesn't have to be able to browse each prerelease that we tested) (done)
12. provide help pages (currently it's only provide it for multiple file upload)
13. integrate multiple test upload in the Web application (done)
14. extend multiple file upload to be able to upload histograms data sets etc.,
15. provide xml description of histograms, data sets etc. to be used by upload application.
16. display all failures modes of multiple test upload to the user and provide comprehensible error message (instead of e.g the error log
    of the web application server that can't be accessed by the user) (done, Hans)
17. there is a special dummy testdes (named "placeholder") which doesn't need to be displayed. In general don't display tests which have 0 entries.

Tasks related to automated testing (ctest/cdash integration):

Currently the infrastructure to include physics tests is being included in the Geant4 CTest/CDash system which provides Nightly and Continuous Integration Testing on different computing platforms. This is intended for tests that don't require huge CPU resources. The plan is to streamline the Physics validation beyond the monthly reference release.