-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to FST geometry to add a simplified version of the geometry for tracking #147
Conversation
update from upstream on Friday, June 11, 2021
Updated StarGeo.xml to be able to acces this in dev2021
…er, heatsinks (draft) )
… rotation of middle disk
This includes material changes
…in PEEK bases, removed unnecessary code
…plified cooling tube connectors)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor issues noted, but no need to hold this.
StarVMC/Geometry/FstmGeo/FstmGeo.xml
Outdated
@@ -424,7 +429,8 @@ The inner support ring (3D printed) should be added | |||
<var name="rmin" value="4.1" /> | |||
<var name="rmax" value="34.00" /> | |||
<var name="dz" value="30.0" /> | |||
<var name="zdisk" value="{144.633,158.204,171.271}" /> | |||
<!-- <var name="zdisk" value="{144.633,158.204,171.271}" /> --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Legacy positions commented out... may be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be removed; maybe changed after survey is understood
for stainless tube and coolant. Will remove lots of tiny volumes. | ||
|
||
The inner support ring (3D printed) should be added | ||
The inner support ring (3D printed) should be added (done) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But... volume FSIR is the inner support ring...
@@ -37,7 +43,6 @@ The inner support ring (3D printed) should be added | |||
|
|||
FTUO, <!-- Tube segment for FST half ring outside wedge container --> | |||
FTUR, <!-- Tube segment for FST half ring inside wedge container --> | |||
FSIR, <!-- Inner support Ring --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... and the inner support ring is removed? Seems inconsistent with the comment above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the assembly of the real detector was done the ring had to be removed. For cleanness the note shuld be revised.
--> | ||
|
||
|
||
<Structure name="mothervol" comment="tubes for the mother volume"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, structure naming conventions follow the naming convention for volumes. Four letters, case insensitive. This is due to FORtran memory management constraints (aka ZEBRA). So...
If you only need this geometry for reconstruction, no action is required.
If you think you would ever run simulations with this geometry, then minimally each structure should start with four unique characters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure that these data structures need to be 4 characters? I am pretty sure this geometry works in starsim, since that what was used in the last 1.5 year by me for checking it out. In the FstmGeo.F the structure variable do show up with the full name length.
<var name="z(2)" type="float" /> | ||
</Structure> | ||
|
||
<Structure name="outerhybrida" comment="outer hybrid a"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Outer and inner hybrids A vs B is where starsim would have a problem. If you think you might want to run a simulation based on this geometry, you should consider renaming these structures.
<Construct sys="stgm" config="STGCv1" /> | ||
<!-- Construct sys="etof" config="ETOFv14f" --> | ||
<Construct sys="wcal" config="WCALv1" simu="1" /> | ||
<Construct sys="hcal" config="HCALv1" simu="1" /> | ||
<Construct sys="plat" config="PLATon" simu="2" /> | ||
<Construct sys="pres" config="PRESv1" simu="2" /> | ||
<Construct sys="pres" config="PRESof" simu="2" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flemming reminded me that preshower detector is not planned for running.
StarVMC/xgeometry/.gitignore
Outdated
@@ -0,0 +1 @@ | |||
*.age |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not quite (there is one file which should not be ignored) but I'll fix after the PR is accepted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a general comment, you probably don't want to create PRs from main of your fork. If you want to keep your fork in sync with this primary repo, it will be much easier for you to do if you create PRs from a different branch
StarVMC/Geometry/FstmGeo/FstmGeo.xml
Outdated
@@ -15,19 +15,25 @@ Januar 14, 2021 F.Videbaek | |||
There is a bit of missing material at the outer edge of the inner mech structure. I will adjust the outer radiues so the toal mateerial should be ok.(approximately | |||
The outer radius could be make slightly bigger to adjust this. | |||
|
|||
To do: Reve the inner novec part of cooling tube and replace with average material | |||
To do: Reviw the inner novec part of cooling tube and replace with average material |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review?
StarVMC/Geometry/FstmGeo/FstmGeo.xml
Outdated
|
||
July 2021 | ||
It is nesc to move FSTmodules out by 2inch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is necessary (?) ....
<Setup name = "FSTMv1s" | ||
comment= "Simplified configuration for the Forward Silicon Tracker" | ||
module = "FstmGeoS" | ||
onoff = "on" | ||
simu = "2" | ||
> | ||
|
||
</Setup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use spaces for indentation consistently?
StarVMC/StarGeometry/.gitignore
Outdated
*.h | ||
*.cxx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's see if #148 works. If it does we won't be polluting the checked out source with generated files. In any event, we should modify such files in a separate PR outside of this one
|
||
FTUO, <!-- Tube segment for FST half ring outside wedge container --> | ||
FTUR, <!-- Tube segment for FST half ring inside wedge container --> | ||
FSIR, <!-- Inner support Ring --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chnge indent
I believe the only open questions here involve whitespace and typos in comments. Could we either fix these non-issues, or approve and move forward? |
Yes, at this point we should just step in and fix the issues. If I don't see any corrections submitted here, I'll go ahead and fix it later today |
Hi
I have been quite busy the last few weeks, sorry I did not complete.
Will try to do tit this afternoon.
Flemming
…On 2021-09-28 10:18, klendathu2k wrote:
I believe the only open questions here involve whitespace and typos in
comments. Could we either fix these non-issues, or approve and move
forward?
--
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Triage notifications on the go with GitHub Mobile for iOS [3] or
Android [4].
Links:
------
[1] #147 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/AUIALBDU5VAYS2KX5OR77KLUEHFENANCNFSM5EDVMUMQ
[3]
https://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!P4SdNyxKAPE!R2pTy3l5iAHWIin171Kmol768xnJUW66lFzY_8DX5w0-1-Yf5sDNaYLHISuopFMO$
[4]
https://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!P4SdNyxKAPE!R2pTy3l5iAHWIin171Kmol768xnJUW66lFzY_8DX5w0-1-Yf5sDNaYLHIQ66956N$
--
Flemming Videbaek
senior scientist
videbaek @ bnl.gov
Brookhaven National Lab
Physics Department
Bldg 510D
Upton, NY 11973
phone: 631-344-4106
cell : 631-681-1596
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with this
AutoBuld failed tonight: .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:75:12: error: 'FSTM::FSTMv1s' has not been declared void FSTM::FSTMv1s::setup() { ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:81:12: error: 'FSTM::FSTMv1s' has not been declared bool FSTM::FSTMv1s::list() { ^.sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx: In function 'bool list()': .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:82:18: error: 'name' was not declared in this scope LOG_INFO << name() << " " << module() << " simu = 2" << " [" << comment() << "]" << endm; ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:82:37: error: 'module' was not declared in this scope LOG_INFO << name() << " " << module() << " simu = 2" << " [" << comment() << "]" << endm; ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:82:74: error: 'comment' was not declared in this scope LOG_INFO << name() << " " << module() << " simu = 2" << " [" << comment() << "]" << endm; ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx: At global scope: .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:88:17: error: 'FSTM::FSTMv1s' has not been declared AgModule* FSTM::FSTMv1s::construct() { ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx: In function 'AgModule* construct()': .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:89:42: error: 'FSTM::FSTMv1s' has not been declared LOG_INFO << "Construct module " << FSTM::FSTMv1s::module() << endm; ^ .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:91:32: error: 'New' was not declared in this scope AgModule* _module = New(); ^ In file included from ./StarVMC/StarAgmlLib/AgBlock.h:17:0, from ./StarVMC/StarAgmlLib/AgModule.h:4, from ./StarVMC/StarGeometry/FstmGeo.h:17, from ./StarVMC/StarGeometry/FstmConfig.h:3, from .sl73_gcc485/obj/StarVMC/StarGeometry/FstmConfig.cxx:1: ./StarVMC/StarAgmlLib/AgMath.h: At global scope: |
No description provided.