# Report On SAMGrid for CDF

Rick St. Denis August 30, 2004

# Progress Towards CDF Adoption of SAM

-   Passed through golden datasets: 59000 files 49TB. 36 crashes.

-   Recovery dataset command works except

    -   If crash or reboot when file released but next not open

    -   If crash or reboot when last file released and output corrupted

    -   If insufficient room for output to go to user

-   Released with new software for station, dbserver, schema with mods
    for CDF etc. (sam v_6)

-   Tested non-golden data to ensure tape mounting ok: get few seconds
    to 20 minutes from arrival of Dcap url to file open.

-   Able to run with delivery of 250 files per minute. (15TB/Hr
    equivalent) Neglible load on DBServer, station, small load on
    database machine. Takes 1 hr to start all 50 projects. DBServer in
    Python proving to be slow.

-   Users get warnings if they will need \>500 files from tape. Daemon
    to watch users. User's volunteered to move to sam.

-   Confusion about v5 and v6 -- some functionality only in v5.

-   Version and release control not under control (at least 1 wk delay)

-   Items remaining

    -   New sam store, change of upload program that gets metadata into
        py file

    -   Limit of 999 files in a recovery dataset

    -   Get users using this on a daily basis.

    -   User instructions that are friendly as CAF instructions.

    -   Daily plots and volumes broken since June 15.

-   Significant delay as developers refused to maintain old code or look
    at bugs. Also, tested new code instead of old (without telling).

-   Unable to get written reports/descriptions/analysis needed to
    convince CDF collaboration we are ready.

-   Had to do most of the testing myself

-   Very negative reaction from Belforte concerning SAM

    -   Could not recommend it

    -   Unable to recover errors easily (particularly ran out of disk
        and needed to rerun)

    -   Condor CAF wastes first 10 min to avoid preemption

    -   Needed splitting of datasets into smaller chunks

    -   Ran with projects lasting 2 weeks: hard to cleanup

-   User support structure needed to be put in place

    -   Shifter training for real users

    -   Present shifters more experts than to answer csh vs sh problems

    -   Need credit for shifters in CDF: referred to Rsnider, need Pasha

-   CDF Analysis still relies heavily on private text files

# Progress Report on Pinning of Datasets

-   Datasets pinned.http://hexfm1.rutgers.edu/DATA_INFO/sam_data/ (about
    26TB, 16TB not available on DCAF (need Grid))

-   Need sam commands (done with scripts)

-   Not heavy offsite usage since it requires users to go to SAM and
    they don't do that yet.

-   Disk fragmentation issues arose -- need to implement recommendations

# Progress on Monte Carlo Storage of files to SAM

-   Able to read without SAM but using Dcache -- needs a software
    release, waiting on tag from Dmitri. Held up for 1 month by Fedor.
    Had to code with Randy for 1 week.

-   Part of DFC migration: painful, little cooperation from Dmitri,
    Fedor; Randy C++ out of date.

-   Sam store with new V6 not in scripts that were given -- need to
    convert.

-   Delayed mainly because of inability to read back without using sam.

-   Private Scripts emailed around: still regarded as correct by many.

# Deployment of JIM

-   Igor able to run CDF MC on Wisconsin cluster and on samg test. 1000
    events, 300 pass filters.

-   Nobody else able to run

-   Unable to install offsite after 1-2 months of trying.

-   Turned to documentation and making an easier one button install --
    much opposed by developers.

-   Wish to

    -   Get one working installation with Experts.

        -   Students and Valeria able to make progress

        -   Without students, progress gone

        -   Gabriele plans to use this to train new students

    -   Run CDF Jobs on that station: turn over to Morag to submit some
        jobs then to Stan(Programmer-physicist) to run MC for Saverio
        (CDF B-MC). Then to Saverio.

    -   Use test setup for tuning up install

    -   Install at Glasgow, then Karlsruhe, then Texas.

-   Morag going: transfer to metadata WG (Tony Doyle) with position:
    agree on goals to be consistent with SAMGrid. She was unable to cope
    with frustration of trying to install JIM

-   Valeria got frustrated -- moved her to installing Grid3 as
    advertised to take 4h.

-   Igor gone, Gabriele priorities:

    -   New students (can use this to train them)

    -   Durable Cache (part of JIM concatenation efforts with D0 MC)

    -   CDF Grid (but Valeria?)

    -   D0 Reconstruction

    -   Further D0 MC sites

# Future of SAMGrid and Factorizing

-   Issue of what Frank Wuerthwein can contribute

-   Brain Storm with Ian Fisk

    -   Use pure Grid3: Valeria will see what this gets

    -   Use SAMGrid as portal to Grid3: ask Gabriele (simple config
        issue when Oxford going?)

    -   CafExe communicates with user -- it is a static workflow manager
        with communication ability: use this with JIM and SAM.

-   Ongoing discussion for the next weeks. I would envisage a 9-sept
    open discussion to set forth a program of studies with conclusion by
    Christmas on what is best for Run II to go forward. CDF to form
    opinion.

-   Very negative mail from Frank regarding sam management and inability
    to separate out projects.

-   Contribution of SAMGrid to OSG: a functioning end to end product
    that has pieces that should be preserved

# 

# Organization

-   For the first time CD has a unified goal: grid. Why is organization
    not on the basis of the "work packages". Some overlap, but need a
    coherent mapping of groups to Grid architecture. Need a czar, not a
    committee.

-   The physics efforts of CD is not obvious: people in CD do not seem
    to report to physics and this is harmful. Products should be
    delivered within CD to CD physics efforts, then to PPE liaisons with
    CD then to physics groups.

-   Need to divide amongst

    -   Parts of grid services that need to be integrated: a Grid
        services integration group

    -   Parts of grid services that FNAL will own

    -   All should go to SourceForge.