TOF Coordinator Meeting

US/Eastern
https://zoom.us/j/92539460351?pwd=715FFQU3G41GQFFMhmIeyUw6Kbk3bM.1 (zoom)

https://zoom.us/j/92539460351?pwd=715FFQU3G41GQFFMhmIeyUw6Kbk3bM.1

zoom

Meeting ID: 925 3946 0351 Passcode: 175932
Description

Weekly ePIC TOF Coordinators/DSL meeting on cost/schedule and plans

Zhangbu Xu
    • 20:00 20:20
      preTDR editing 20m

      https://www.overleaf.com/project/66e0603e1fc718e728c9d072

      Below are the minutes from our Zoom discussion on the TOF chapter, with a focus on what we must do next.
      Please reply with any corrections or updates.

      MINUTES (Summary)
            1.    Purpose
            •     Rework the TOF chapter (for pre-TDR/TVR) so it is reader-friendly and ready for the review committee.
            2.    Schedule (hard dates)
            •     Review Committee meets: November 12–14, 2025.
            •     We aim to send the document by October 31, 2025 to allow a short editorial pass before submission.
            3.    Decisions / Principles
            •     Separate requirements (physics-driven) from technology (solutions). Keep requirements technology-agnostic. Radiation tolerance should state expected levels by region; AC-LGAD and other R&D specifics go in the performance/technology sections.
            •     Split ES&H and QA; integrate QA with manufacturing/assembly plan.
            •     Rename “Risks & Mitigation” to “Technological Challenges and Path Forward.”
            •     De-emphasize R&D lists (R&D formally ends in 2025); refer only to results needed for the chapter’s arguments.
            •     Avoid concrete calendar dates in the text (e.g., “Q1 2025”); prefer stage/phase descriptions.
            •     Centralize electronics/ASIC/readout general content in a single electronics overview; detector chapters should reference rather than duplicate.
            •     Remove values for other subsystems (e.g., B0) from TOF tables; place them in their own sections to avoid duplication/inconsistency.
            •     Verify and align all numbers (channel counts, areas, coverage, etc.) across text, tables, and figures.
            •     Improve readability: add a sensor “cartoon” figure and reduce unnecessary acronyms.

      WHAT WE MUST DO NEXT (Action Items)

      Owner: Zhangbu & Satoshi
      Task: Restructure the full chapter to cleanly separate Requirements / Technology / Performance, relocate ES&H/QA as agreed, and apply the new “Technological Challenges and Path Forward” section title.
      Notes: This is the backbone edit that other items depend on.

      Owner: Zhangbu & Satoshi
      Task: Remove non-TOF subsystem values (e.g., B0) from TOF tables and move them to their own sections; ensure technology descriptions appear only once in the correct place.
      Notes: Prevent cross-chapter duplication and conflicting numbers.

      Owner: Zhangbu & Satoshi
      Task: Audit and harmonize all quantitative entries (channel counts, areas, acceptance, fluence assumptions, etc.) across text, figures, and tables.
      Notes: Provide a one-page “numbers sheet” as source of truth.

      Owner: Satoshi
      Task: Provide a clear sensor cartoon (or simplify an existing one) for the intro/system explanation.
      Notes: Keep text modest; include callouts only for essentials.

      Owner: Simone
      Task: Update/confirm fluence-related plots; ensure latest inputs, labels, and conditions are explicit.
      Notes: Include caption text stating source, assumptions, and units.

      Owner: All contributors
      Task: Acronym cleanup: define on first use; remove non-essential acronyms; use plain terms where practical.
      Notes: Provide an acronym list if truly needed.

      Owner: Electronics (Wei & Tonko)
      Task: Consolidate ASIC/readout general discussion into the electronics overview; in detector chapters, keep only minimal, relevant references and measured performance.
      Notes: Avoid diagram elements that are no longer part of the design (e.g., remove FPGA blocks if obsolete).

      Owner: Zhangbu & Satoshi → Silvia&John
      Task: Share progress updates and ensure there is editorial time before submission.
      Notes: Short pre-submission pass to catch structure/consistency issues.

      Owner: All contributors
      Task: Avoid specific calendar dates in prose where possible; describe steps by phase/milestone.
      Notes: Keeps the chapter resilient to schedule shifts.

      OPEN / FOLLOW-UPS
            •     Re-classify any ambiguous figures (e.g., system vs. performance) into the correct sections.
            •     Confirm current readout board architecture in figures (e.g., remove FPGA blocks if not used).
            •     In TOF text, clearly signpost BTOF vs. FTOF and avoid repeating common material.

      TIMELINE REMINDER
            •     Internal restructuring and figure/number updates → editorial pass in late October.
            •     Submission by Oct 31, 2025 → Review Committee Nov 12–14, 2025.

      If you own an item above, please confirm feasibility and flag blockers ASAP.

      Best regards,
      Satoshi

    • 20:20 20:40
      PED26 20m
    • 20:40 21:00
      Mechanic Design and Stave Design 20m
    • 21:00 21:20
      test beam at DESY 20m

      test both strips and pixel
      JLab test for strips not optimal.

      timing detectors from BELLE2 meeting
      https://drive.google.com/drive/folders/11UdsdY3eUtxNAvC1XCzE287uhhPWKk51

      new strip sensors will be tested.

      A new call for proposals for beam time at NLCTA through BeamNetUS is open.

      The BeamNetUS program awards beam time (up to 3 weeks per experiment) and covers travel expenses for Users. Beam time will be scheduled in April – September 2026. ... Facility capabilities at NLCTA include electron beam from the XTA beamline delivered in air or in vacuum and dedicated test areas for high-power RF testing at 2.856 GHz or 11.424 GHz at temperatures down to 4 K or external magnetic fields up to 5 T.
      Proposal template (6 pages) and submission portal is open here: https://www.beamnetus.org/access
      The deadline for proposal submissions is November 30th, 2025