Hi Joerg,
many thanks for prompt reaction!

<snip>

> In the current configuration the script will print out only even run numbers. 
> If you want to change it, adjust this variable:
>
> my $selectruns = "even"; #odd even chose "" for all runs

I think there will be enough data toalign with even runs - use odds for 
validation...

> - The job in mp0789 is configured to use isolated muons. If you want to use 
> other data sets you might have to use a different .py file (and of course 
> changes have to be applied in setup_align.pl accordingly).
>
> - One important issue: You have to configure the IOV boundaries in 
> alignables.txt . Add something like
>
> process.AlignmentProducer.RunRangeSelection = [
>    cms.PSet(RunRanges = cms.vstring('-1:158383',
>                                     '158384:161406',
>                                     '161407:162974',
>                                     '163078:164060',
>                                     '164162:165408',
>                                     '165415:165999',
>                                     '166004:166396',
>                                     '166399:167029',
>                                     '167033:-1'
>                                     ),
>             selector = cms.vstring('TrackerTPBLayer,111111',
>                                    'TrackerTPEHalfDisk,111111')
>             ),
>    ]
>
>
> to alignables.txt whereas of course the numbers have to be adjusted.

This run number selection might not be needed at first hand - just make 
two separate input file lists forteh two periods mentioned in Alessio's 
talk. The exact run number boundary will later come from Andrew.

If you understand all the procedures, it might be easiest to run 
everything in one go, making two IOVs by selecting run numbers...

Cheers

 	Gero

> Hope thats all and I have not forgotten anything ...
>
> Cheers,
> Joerg
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>> 
>> But you will also have to run offline validation, as has been done for
>> the sign-off, so you are probably aware of how to do that - you could
>> already start to look for the relevant files, i.e. data after beginniung
>> of July. For datasets see
>> https://twiki.cern.ch/twiki/bin/viewauth/CMS/TrackerAlignment2011#Lists_of_2011_Collision_Datasets
>> 
>> 
>> Cheers
>> 
>> Gero
>>> 
>>> Cheers
>>> 
>>> gv
>>> On Mon, 19 Sep 2011, Gero Flucke wrote:
>>> 
>>>> Dear Hungarian aligners,
>>>> you are probably aware that the pixel detector seems to have slightly
>>>> moved at least twice since end of June (day 180), i.e. the last data
>>>> included in our currently signed-off alignment, see at lower right
>>>> plot of http://musich.web.cern.ch/musich/CronPVValidation/
>>>> 
>>>> Since reprocessing is not yet scheduled, there is time to correct for
>>>> that, i.e. to run alignment of the pixel barrel layers and forward
>>>> half discs keeping the strip detecctor fixed.
>>>> 
>>>> Would your group be able to take the responsibility of this task,
>>>> i.e. providing this alignment and its basic validation within the
>>>> next two weeks or so?
>>>> 
>>>> Please answer soon so that we can exchange about details.
>>>> 
>>>> Cheers
>>>> 
>>>> Gero
>>>> 
>>>> --
>>>> -----------------------------------------------------------------------
>>>> Gero Flucke
>>>> - Analysis Centre, Helmholtz Alliance "Physics at the Terascale"
>>>> * Statistics Tools
>>>> - CMS: Tracker Alignment Convenor
>>>> DESY/CMS, Notkestr. 85, D-22607 Hamburg, Germany
>>>> Bldg. 1e, Rm. 02.501
>>>> phone: +49 (0)40 8998 3525
>>>> fax: +49 (0)40 8998 3092
>>>> 
>>> 
>> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

-- 
-----------------------------------------------------------------------
Gero Flucke
    - Analysis Centre, Helmholtz Alliance "Physics at the Terascale"
       * Statistics Tools
    - CMS: Tracker Alignment Convenor
DESY/CMS, Notkestr. 85, D-22607 Hamburg, Germany
Bldg. 1e, Rm. 02.501
phone: +49 (0)40 8998 3525
fax:   +49 (0)40 8998 3092