Difference between revisions of "Amrita's Progress"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
(Blanked the page)
 
(15 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Task List =
 
  
<b><font size="large" color="red">Document everything that you do or investigate</font></b>
 
 
* Complete the XML documentation on the CLAS12 Software Wiki.
 
** Document each of the possible elements, i.e. <box>, <tube> etc. Document which parameters go with each shape
 
** Document how you specify material and other properties.
 
** Document how you specify a magnetic field.
 
** (More difficult) Is there a method to mark a region as active?
 
 
* We can run Sim12 with -G and type commands. Create a new page on the CLAS12 wiki on how to use this mode.
 
** Document some of the most useful commands, i.e. "set the angles" "set the zoom level", "set the x,y position", "turn visibility on/off" "change color of element", "change shading of element". All this can be found in the proper GEANT4 documentation. Link to that documentation.
 
** Write one (or several) .mac scripts that display the detector. For an example of reasonable displays see [http://clasweb.jlab.org/12gev/software/geant/]
 
** Write some .mac scripts that display the central detector only.
 
 
* To get further on the track debugging:
 
** There was a suggestion that the problem was caused by the "npos" command which positions multiple copies of something. We want to test this.
 
*** Create an XML document that only contains a single "sector" (wedge shape of the CLAS12 detector) with nothing in it. Test this to see if this causes a stuck track problem
 
*** Next npos this wedge 6 times, just as done with CLAS12. See if the problem now appears. (Difficult question:) If so, what is wrong with the npos implementation.
 
*** If that works, is there anything positioned in the CLAS12 wedges (in clas12.xml) that sticks out of the wedge, even is ever so slightly. Is it even possible to have something stick out?
 
** (Difficult task:) The relevant code for studying Sim12 is all in the sub directory, "src", not in the Sim12.cc code. You would probably need to get some help if you want to attempt these:
 
*** Modify the Sim12 stepping class to print out something every step. What information is available in these classes? What can we print out?
 
*** Go to the GEANT4 documentation to learn about how steps are done and how to retreive information about a step.
 
*** Run the modified code and then go through all the output to see if we can find what location the track is reported as being stuck.
 
 
* Look at the implementation of the SVT (in the central detector, the silicon strip readout layers) in the clas12.xml code.
 
** How is is implemented? What is one detector element build up from? A single rectangular box, a sandwitched box?
 
** Make some pictures of the SVT using the Sim12 code.
 
** (Difficult task:) How can we get "readout" from this device? What do we need to do to get readout?
 
** Go to the GEANT4 documentation and learn about how we can read out the amount of energy deposited in a volume due to a particle passing through it.
 
** (Very difficult task:) Implement an SVT readout scheme.
 
 
= Progress =
 
 
=== Monday June 18 ===
 
Starting with xml documentation
 
documenting all possible elements
 
Going through HDDS ,geometric detector specification
 
continuing with the same task
 
=== Tuesday June 19th ===
 
started with xml documentation
 
leaving
 
* <b><font color="red">Do not forget to maintain this page. Especially "sign in" and "sign out", so that we can track your hours.</font></b><br> If you do not, how can I know you are keeping track of your time.
 
===wednesday june 20th===
 
arrived
 
writing how to make a volume using xml
 
===thursday june 21st===
 
going through the GEANT4 documentation
 
===friday june 22nd===
 
arrived
 
writing the xml program for making a volume element of detector
 
===monday june 25th===
 
===tuesday june 26th===
 
making a simple xml file to get a simple volume
 
 
trying to figure out where the error is in the xml file
 
 
still stuck
 
 
created a xml file tat gives a bigger box and a smaller one inside it,still some segmentation fault,not able to pass a beam through the volume
 
 
writing how to specify materials in a xml document
 
 
done with writing about the material specification and making a self sufficient my.xml fie....with the materials incuded in the file.
 
 
leaving
 
===wednesday june 27th===
 
arrived
 
 
completing the XML documentation on the wiki page
 
 
writing how to include magnetic field
 
 
looking at the track debugging problem
 
 
searching for commands to make a .mac script
 
 
not able to find the Sim12detectorconstructionMassenger.cc to get the commands for creating the .mac file
 
 
got the Sim12detectorMassenger.hh file,looking at the commands.
 
 
going through the various commands in gui.tcl
 
===thursday june 28th===
 
arrived
 
 
looking at the track problem after reading the mails in the group
 
 
looking at the various commands,by opening the gui of clas12.xml
 
 
tried to make the two volumes sensittive but this does not work
 
 
making a .mac script
 
 
===friday june 29th===
 
.mac script
 
 
The requested URL /geant4/UserDocumentation/UsersGuides/ForApplicationDeveloper/html82/Control/commands.html was not found on this server. not able to open the link suddenly.
 
 
working with the my.xml code
 
 
made a simple xml file with jus a boz and a tube inside it and 6 wedges.
 
 
Discussed the stuck tract problem with the clas12.xml with professor maurik and solved it
 
===monday july 2nd===
 
looking at the commands in gui.tcl
 
 
writing .mac script
 
 
continuing with the same work
 
 
leaving
 
===tuesday july 3rd===
 
arrived
 
 
looking at the .mac files in mac_files folder
 
 
same work
 
===thursday july 5th===
 
arrived
 
 
writing .mac file
 
 
same work
 
===friday july 6th===
 
arrived
 
 
reading the newgeom.mac script
 
 
creating a .mac script
 
 
not able to run my.mac script
 
 
leaving
 
===monday july 9th===
 
arrived
 
 
.mac script
 
 
same work
 
===tuesday july 10th===
 
 
arrived
 
 
documenting the commands
 
 
continuing
 
===wednesday july 11th===
 
 
arrived
 
 
documenting various built in commands
 
 
same task
 

Latest revision as of 13:51, 5 November 2020