Difference: CmsSw (1 vs. 6)

Revision 62007-11-11 - FerencSikler

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="TrackerSoftware"
>
>
META TOPICPARENT name="Trash.CMSTrackerSoftware"
 

CMSSW

  • Basic concept: CMSSW is the current official CMS simulation and reconstruction software framework. There are various modules (shared object files), which are dynamically linked to a main binary (called cmsRun), which is not touched at all by the user. These modules can be switched on/off and can be configured by job config files. It runs like this: cmsRun job_config_file.cfg. One can also say this in an other way: the cmsRun interprets the job config file. One can also extend or modify the software by creating/modifying the modules.

Revision 52006-06-21 - BalintRadics

Line: 1 to 1
 
META TOPICPARENT name="TrackerSoftware"

CMSSW

Line: 19 to 19
 -- BalintRadics - 19 Jun 2006

Added:
>
>
  • CMSSW tutorial held at Cern on 21 June 2006: Tutorial

-- BalintRadics - 21 Jun 2006

 
META FILEATTACHMENT attr="" autoattached="1" comment="Some test file samples" date="1150552406" name="DemoAnalyzer.tar.gz" path="DemoAnalyzer.tar.gz" size="9640" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="cmssw install script" date="1150552451" name="install_cmssw.sh" path="install_cmssw.sh" size="1042" user="Main.AndrasLaszlo" version="1"
META TOPICMOVED by="AndrasLaszlo" date="1150553109" from="CMS.CMSSW" to="CMS.CmsSw"

Revision 42006-06-20 - FerencSikler

Line: 1 to 1
 
META TOPICPARENT name="TrackerSoftware"
Added:
>
>

CMSSW

 
  • Basic concept: CMSSW is the current official CMS simulation and reconstruction software framework. There are various modules (shared object files), which are dynamically linked to a main binary (called cmsRun), which is not touched at all by the user. These modules can be switched on/off and can be configured by job config files. It runs like this: cmsRun job_config_file.cfg. One can also say this in an other way: the cmsRun interprets the job config file. One can also extend or modify the software by creating/modifying the modules.
  • Some useful links: twiki, software cross reference, config language manual, useful samples.
  • How to check out and use: download the files install_cmssw.sh and DemoAnalyzer.tar.gz, then run the install_cmssw.sh install script. Check the directory CMSSW_*_*_*/src/Demo/DemoAnalyzer. Under the bin directory I put a quasi-automated job runner script called go.sh. Under the test directory, there are job config sample files, like: single muon sample generation by particle gun + simulation + digitalization, local reconstruction (hit collection), and CTF-KF track finding.
Line: 5 to 7
 
  • How to check out and use: download the files install_cmssw.sh and DemoAnalyzer.tar.gz, then run the install_cmssw.sh install script. Check the directory CMSSW_*_*_*/src/Demo/DemoAnalyzer. Under the bin directory I put a quasi-automated job runner script called go.sh. Under the test directory, there are job config sample files, like: single muon sample generation by particle gun + simulation + digitalization, local reconstruction (hit collection), and CTF-KF track finding.
  • We have set up a mailing list on CMSSW at cmssw@NOSPAMszofi.elte.hu. For subscribing, send a mail with subject subscribe. For unsubscribing, send a mail with subject unsubscribe.
Deleted:
<
<
 -- AndrasLaszlo - 17 Jun 2006
Changed:
<
<
  • Here are some usefull links (without any concept):
>
>
  • Here are some useful links (without any concept):
  * Reconstruction * High Level Trigger * HLT Global Object

Revision 32006-06-19 - BalintRadics

Line: 1 to 1
 
META TOPICPARENT name="TrackerSoftware"
  • Basic concept: CMSSW is the current official CMS simulation and reconstruction software framework. There are various modules (shared object files), which are dynamically linked to a main binary (called cmsRun), which is not touched at all by the user. These modules can be switched on/off and can be configured by job config files. It runs like this: cmsRun job_config_file.cfg. One can also say this in an other way: the cmsRun interprets the job config file. One can also extend or modify the software by creating/modifying the modules.
  • Some useful links: twiki, software cross reference, config language manual, useful samples.
Line: 9 to 9
 -- AndrasLaszlo - 17 Jun 2006
Added:
>
>

-- BalintRadics - 19 Jun 2006

 
META FILEATTACHMENT attr="" autoattached="1" comment="Some test file samples" date="1150552406" name="DemoAnalyzer.tar.gz" path="DemoAnalyzer.tar.gz" size="9640" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="cmssw install script" date="1150552451" name="install_cmssw.sh" path="install_cmssw.sh" size="1042" user="Main.AndrasLaszlo" version="1"
META TOPICMOVED by="AndrasLaszlo" date="1150553109" from="CMS.CMSSW" to="CMS.CmsSw"

Revision 22006-06-17 - AndrasLaszlo

Line: 1 to 1
 
META TOPICPARENT name="TrackerSoftware"
  • Basic concept: CMSSW is the current official CMS simulation and reconstruction software framework. There are various modules (shared object files), which are dynamically linked to a main binary (called cmsRun), which is not touched at all by the user. These modules can be switched on/off and can be configured by job config files. It runs like this: cmsRun job_config_file.cfg. One can also say this in an other way: the cmsRun interprets the job config file. One can also extend or modify the software by creating/modifying the modules.
  • Some useful links: twiki, software cross reference, config language manual, useful samples.
  • How to check out and use: download the files install_cmssw.sh and DemoAnalyzer.tar.gz, then run the install_cmssw.sh install script. Check the directory CMSSW_*_*_*/src/Demo/DemoAnalyzer. Under the bin directory I put a quasi-automated job runner script called go.sh. Under the test directory, there are job config sample files, like: single muon sample generation by particle gun + simulation + digitalization, local reconstruction (hit collection), and CTF-KF track finding.
Changed:
<
<
  • We will set up soon a mailing list on CMSSW.
>
>
  • We have set up a mailing list on CMSSW at cmssw@NOSPAMszofi.elte.hu. For subscribing, send a mail with subject subscribe. For unsubscribing, send a mail with subject unsubscribe.
 

-- AndrasLaszlo - 17 Jun 2006

Revision 12006-06-17 - AndrasLaszlo

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="TrackerSoftware"
  • Basic concept: CMSSW is the current official CMS simulation and reconstruction software framework. There are various modules (shared object files), which are dynamically linked to a main binary (called cmsRun), which is not touched at all by the user. These modules can be switched on/off and can be configured by job config files. It runs like this: cmsRun job_config_file.cfg. One can also say this in an other way: the cmsRun interprets the job config file. One can also extend or modify the software by creating/modifying the modules.
  • Some useful links: twiki, software cross reference, config language manual, useful samples.
  • How to check out and use: download the files install_cmssw.sh and DemoAnalyzer.tar.gz, then run the install_cmssw.sh install script. Check the directory CMSSW_*_*_*/src/Demo/DemoAnalyzer. Under the bin directory I put a quasi-automated job runner script called go.sh. Under the test directory, there are job config sample files, like: single muon sample generation by particle gun + simulation + digitalization, local reconstruction (hit collection), and CTF-KF track finding.
  • We will set up soon a mailing list on CMSSW.

-- AndrasLaszlo - 17 Jun 2006

META FILEATTACHMENT attr="" autoattached="1" comment="Some test file samples" date="1150552406" name="DemoAnalyzer.tar.gz" path="DemoAnalyzer.tar.gz" size="9640" user="Main.AndrasLaszlo" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="cmssw install script" date="1150552451" name="install_cmssw.sh" path="install_cmssw.sh" size="1042" user="Main.AndrasLaszlo" version="1"
META TOPICMOVED by="AndrasLaszlo" date="1150553109" from="CMS.CMSSW" to="CMS.CmsSw"
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback