Geant4-MT migration and UI issues - PowerPoint PPT Presentation

jubal
geant4 mt migration and ui issues n.
Skip this Video
Loading SlideShow in 5 Seconds..
Geant4-MT migration and UI issues PowerPoint Presentation
Download Presentation
Geant4-MT migration and UI issues

play fullscreen
1 / 6
Download Presentation
Geant4-MT migration and UI issues
84 Views
Download Presentation

Geant4-MT migration and UI issues

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Geant4-MT migration and UI issues K. Murakami (KEK/CRC) 17th Geant4 Collaboration meeting

  2. Scope of UI • Interfaces ("session") • terminal frontend (CL), GUI • batch • Intercoms • UI command mechanism 17th Geant4 Collaboration meeting

  3. Outlook of Session and G4MT • Current MT does not use UIsession (CL, GUI) • Use UIbatch • instantiated in each thread by macro execution. • UImanager (thread local) dispatches UI commands. • UI session (CL,GUI) is completely decoupled with the G4 kernel. • UI sessions themselves are not affected by MT. • Open issues: • session is thread-out / run on main thread? • UIbatch is free from UIsession? 17th Geant4 Collaboration meeting

  4. Some complexity • Session instance: • should be one for CL, GUI • #threads for Batch • UImanager of each thread can dispatch UIcommands. • How to distribute UIcommands in each thread for CL/GUI session? • Some kind of thread manager is necessary. • To know the pointer of UImanager in each thread 17th Geant4 Collaboration meeting

  5. Other issues on UIsession • Session outputs should be taken care. • output with thread-ID prefix • divided file outputs by thread-ID • kinds of efforts already done • G4coutDistination A minor concern: • In case that the "run" of main thread is ended prior to other threads, • Command prompt is back to the session? • Parallel run manager makes thread-sync? • maybe yes,should be double-checked • For the case that session is thread out, • more rigorous status check is necessary fro each command • commands not protected could break application. 17th Geant4 Collaboration meeting

  6. UIcommandscheme • UIcommands are dispatched by the thread-local UImanager in each thread. • Concerns • Once again, remind that the scheme is applicable for single object (per thread) • Don't forget the object is thread-local, thread-wide or thread-different. • thread-local would be ok for most cases • take care for the cases of thread-wide, thread-different • Double check for "thread-safety" of each command 17th Geant4 Collaboration meeting