WIP: development of DetCRD (CEPC Reference Detector)

[mirguest]

• Create a directory under Detector (See commit 4f00fcc)
• Calorimeter (@LinghuiWuIHEP)
  • See PR Add CRD Ecal geometry #32
• Drift Chamber
  • See WIP: start the development of Drift Chamber for CEPC #18

[mirguest]

Hi @LinghuiWuIHEP,

could you create a new issue to track the development status of the calorimeter detector?

Thanks.
Tao

[fucd]

Hi @mirguest and all,

I try to implement base compact files and beampipe as begin of CRD, see PR #44.
In this implement, set a main version ix (i denotes coil inside Hcal, and o will denote coil outside Hcal in future) and a branch version to make up whole detector, like ILD. But many links in ILD are removed to make the parameters more clear.

If any comments or suggestion about it, please let me know.

Chengdong

[mirguest]

Hi @mirguest and all,

I try to implement base compact files and beampipe as begin of CRD, see PR #44.
In this implement, set a main version ix (i denotes coil inside Hcal, and o will denote coil outside Hcal in future) and a branch version to make up whole detector, like ILD. But many links in ILD are removed to make the parameters more clear.

If any comments or suggestion about it, please let me know.

Chengdong

Hi @fucd,
First, thanks for your work.

I think it's better to follow a naming convention for the different detector options.

In lcgeo, I think their convention is option + version (such as CLIC_o3_v05) in CLIC.
The ILD also provides an example to describe their detector options (such as ILD_l5_o1_v02) in their README.

So the meaning of o is actually option. I would suggest to avoid such confusion when you name the detectors.

Tao

[fucd]

Hi @mirguest and all,
I try to implement base compact files and beampipe as begin of CRD, see PR #44.
In this implement, set a main version ix (i denotes coil inside Hcal, and o will denote coil outside Hcal in future) and a branch version to make up whole detector, like ILD. But many links in ILD are removed to make the parameters more clear.
If any comments or suggestion about it, please let me know.
Chengdong

Hi @fucd,
First, thanks for your work.

I think it's better to follow a naming convention for the different detector options.

In lcgeo, I think their convention is option + version (such as CLIC_o3_v05) in CLIC.
The ILD also provides an example to describe their detector options (such as ILD_l5_o1_v02) in their README.

So the meaning of o is actually option. I would suggest to avoid such confusion when you name the detectors.

Tao

Hi @mirguest

Thanks for your comments. The option versions are divided as simulation and reconstruction. In ILD, as my understood, ILD_l5_v02 denotes simulation option, and then it will extension to several reconstruction-relative options (such as ILD_l5_o1_v02). Currently, CRD_i1_v01
is simulation-based version. It has also described in Detector/DetCRD/compact/README.md, and will be extended continuously.

Chengdong

[fucd]

According to version name rule, cancel #44, now apply PR #82