Print

Print


Commit in lcdd/doc on MAIN
README-141.1 removed
gdml_add_tag.txt-951.2 removed
gdml_changes.txt-51.1 removed
release_notes/lcdd_release_notes_1_12_0.html-1051.2 removed
-219
4 removed files
remove old stuff from doc dir

lcdd/doc
README removed after 1.1
diff -N README
--- README	16 Nov 2004 03:42:52 -0000	1.1
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,14 +0,0 @@
-Directories:
-
-Schemas - XML schemas
-bin - binary
-config - make fragments
-extern - GDML tarball
-include - includes
-lcdd.cc - "sample" main
-lib - library (x1)
-macros - G4 macros
-scripts - shell scripts
-setup-lcdd-slac.sh - setup script
-src - cc sources
-tmp - temp (for build)

lcdd/doc
gdml_add_tag.txt removed after 1.2
diff -N gdml_add_tag.txt
--- gdml_add_tag.txt	13 Jan 2005 00:53:44 -0000	1.2
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,95 +0,0 @@
-_HowTo Add a New Tag to GDML_
-
-Following the strategies in Radovan Chytracek's C++
-implementation of the GDML processor, here are the 
-steps to add a generic tag "t" to a GDML schema and 
-process it in your application.
-
-# add t and attrib/child elements to the extended schema document and test/validate
-
-# add t to gdml "test file" and test/validate
-
-# required (or at least highly recommended) C++ classes for t will usually include...
-  # tType
-    # type from the schema
-    # maybe it has no parent class if the type doesn't
-    # get/set for common attributes
-    # get/set_content methods if it has children (see, for instance, VolumeType.h)
-  # t
-    # element of type tType
-    # inherits from tType and SAXObject
-    # may or may not implement get/set methods, depending on if these were put in the tType interface
-  # tProcess
-    # data interface to subscribers
-    # inherits from SAXStateProcess or tTypeProcess (if exists)
-  # tSubscriber
-    # subscriber to create application objects from SAXObject
-    # inherits from SAXSubscriber
-
-# create tProcess
-
-  # StartElement
-    # new t
-    # m_obj = t
-    # topObject = *Context()->GetTopObject() = t
-    # parent::EndElement(..) [if exists]
-      # parent element *should not* set m_obj/topObject, only common attribute settings!
-
-  # StackPopNotify [if applicable]
-    # add children using set_content
-
-  # DECLARE_PROCESS_FACTORY(tProcess)
-
-  # State()
-    # return "t" as str
-
-# add LOAD_COMPONENT(tProcess) to UserLoad()
-
-# create tSubscriber
-
-  # Activate()
-
-    # dynamic cast SAXObject to t
-
-    # if cast = ok, create application object tObj from t's process data
-      # use tProcess->set_() methods
-      # do expression evaluation using GDMLExpressionEvaluator
-      # lookup referenced elements using ref->get_ref()
-      # add to GDML object stores in GDMLProcessor [optional]
-
-    # iterate over children using ContentSequence and fill tObj [if
-      applicable] (see VolumeSubscriber, for instance)
-
-  # DECLARE_SUBSCRIBER_FACTORY(tSubscriber)
-
-# add LOAD_COMPONENT(tSubscriber) to UserLoad()
-
-# make sure UserLoad() is called at initialization time
-
-_Caveats and Problems_
-
-# If you add a process to a certain tag, the default GDML process is overridden.  
-  Thus, your process must implement (somehow) all of the behavior of the
-  process it is replacing, including attribute setup and adding children.
-  This can be done through (careful) use of inheritance.
- 
-# The default Activate() methods in subscribers delete the received SAXObject;
-  thus, if you subscribe to GDML objects (not your own), the SAXObject received 
-  will be invalid! (i.e. already deleted)  The only "solution" I have found is to
-  count on the fact that your subscriber will be called after GDML's.  Thus the
-  call to delete can be removed from GDML's subscriber and your's should
-  include it.  This isn't much of a proper solution, and I am waiting on input
-  from Radovan on this.
-
-# If you add a tag that is a child of an existing GDML tag, it may not
-  be available in the parent tag's SAXObject.  This is because the
-  StackPopNotify() function of the child tag's process may check for specific,
-  known child tags.  The workaround is to make the GDML process push your child
-  (or all children) into its content.  The main example of this is
-  SinglePlacementTypeProcess, which looks for two known GDML tags and ignores
-  others, probably your added tag, in my case physvolid.
-
-# Minor build system complaints...
-
-  # gmake doesn't work if arch isn't exact match.  Fake with gmake "SCRAM_ARCH=...".
-  # Geant4 examples hardcode global libs, which may not be built.

lcdd/doc
gdml_changes.txt removed after 1.1
diff -N gdml_changes.txt
--- gdml_changes.txt	13 Jan 2005 01:04:18 -0000	1.1
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,5 +0,0 @@
--geant4/Subscribers/volumeSubscriber.cpp
-  -removed delete (happens in $LCDD_BASE/src/volumeExtendedSubscriber.cc)
-
--Processes/Processes/SinglePlacementTypeProcess.h
-  -"physvolid" to content in StackPopNotify()

lcdd/doc/release_notes
lcdd_release_notes_1_12_0.html removed after 1.2
diff -N lcdd_release_notes_1_12_0.html
--- lcdd_release_notes_1_12_0.html	19 Dec 2006 00:08:10 -0000	1.2
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,105 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<html>
-<head>
-<meta name="generator" content=
-"HTML Tidy for Linux/x86 (vers 1st March 2004), see www.w3.org">
-<title>Release Notes - LCDD 1.12.1</title>
-</head>
-<body>
-
-<p>
-These are the release notes for LCDD 1.12.0 .
-</p>
-
-<p>
-The automatically created links to Jira are listed at the end of the notes.  
-</p>
-
-<h2>Summary of Changes Since Last Release</h2>
-
-<ul>
-<li>Bug fixed in combining tracker hits with G4TrackerCombineSD.  Energy cut is now performed on the final combined hit rather than individual steps.
-<li>Bug fixed in RZBFieldMap where steps at the boundary caused the algorithm to crash.  Action at boundary is now much simpler and doesn't crash.
-<li>Verbose output from sensitive detectors was improved, especially for G4TrackerCombineSD.
-<li>CalorimeterHits can now be aggregated using position or ID of the virtual readout cell.
-<li>A command was added to dump GDML from the command line or macro interface.
-<li>Global field overlay was added and is the default behavior of the field manager.
-<li>Two commands for checking overlaps using the built-in functions of G4LogicalVolume were added to the /lcdd command dir.
-<li>A simple dipole magnet type was added to the LCDD format.
-<li>Interactive commands to loaded sensitive detectors was added in the /detectors macro directory.
-<li>The verbosity of sensitive detectors can be modified at runtime using the /detectors commands.
-</ul>
-
-<h2>Bug</h2>
-<ul>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-63'>LCDD-63</a>] -
-Remove energy cut on single step in G4TrackerCombineSD.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-65'>LCDD-65</a>] -
-MCParticles produced by the simulation without hits are still
-written into the LCIO file.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-66'>LCDD-66</a>] -
-Field map geometry causes slic to crash.</li>
-</ul>
-<h2>Improvement</h2>
-<ul>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-32'>LCDD-32</a>] -
-Improve verbose output of sensitive detectors.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-33'>LCDD-33</a>] -
-Improve printing of Geant4 runtime objects.</li>
-</ul>
-<h2>New Feature</h2>
-<ul>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-3'>LCDD-3</a>] -
-aggregate cal hits by matching IDs OR global coordinates</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-35'>LCDD-35</a>] - Add
-command for dumping GDML.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-43'>LCDD-43</a>] -
-Entity resolution using full paths from URL.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-47'>LCDD-47</a>] -
-dipole magnet</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-48'>LCDD-48</a>] -
-Overlay global magnetic fields.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-50'>LCDD-50</a>] -
-Improved handling of magnetic fields in LCDD.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-61'>LCDD-61</a>] - Add
-macro command to check overlaps of volumes, using the
-CheckOverlaps() function on the physical volume.</li>
-<li>[<a href='https://jira.slac.stanford.edu/browse/LCDD-70'>LCDD-70</a>] - Macro commands for sensitive detectors.</li>
-</ul>
-<h2>Task</h2>
-<ul>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-27'>LCDD-27</a>] - Use
-G4TMP for initial LCDD lib location.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-29'>LCDD-29</a>] -
-Investigate G4Material warning.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-36'>LCDD-36</a>] - GDML
-build on Darwin.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-40'>LCDD-40</a>] -
-Option for setting up schema dir.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-64'>LCDD-64</a>] -
-Verbose setting of sensitive detectors should be a Geant4 macro
-command rather than a value read from the LCDD file.</li>
-<li>[<a href=
-'https://jira.slac.stanford.edu/browse/LCDD-69'>LCDD-69</a>] -
-Prepend include guard define variables with LCDD_ in all header
-files.</li>
-</ul>
-</body>
-</html>
CVSspam 0.2.12


Use REPLY-ALL to reply to list

To unsubscribe from the LCD-CVS list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=LCD-CVS&A=1