Thread: [brlcad-tracker] [ brlcad-Feature Requests-1933724 ] Need NIRT to report target gaps (void spaces)
Open Source Solid Modeling CAD
Brought to you by:
brlcad
From: SourceForge.net <no...@so...> - 2008-04-03 20:05:05
|
Feature Requests item #1933724, was opened at 2008-04-03 16:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Raytrace Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marianne Kunkel (pantano) Assigned to: Nobody/Anonymous (nobody) Summary: Need NIRT to report target gaps (void spaces) Initial Comment: Would like an option for NIRT to explicitly report the xyz of beginning of a target gap (void space in the geometry) and length of that target gap for all target gaps encountered on the shotline. Reason: MUVES-S2 uses an algorithm, called airgap, to determine probability of sustained fire for API (armor piercing incendiary) threats against fuel systems in aircraft. One of the factors in predicting aircraft fires is the length of the target gap between where the munition "functions" (releasing incendiary) and where the munition encounters fuel (or other flammable fluid). Efforts to debug MUVES results would be enhanced if NIRT could automatically report target gaps to the user. This would also help target describers validate target descriptions of fuel systems and the target gaps(called aircraft dry bays) surrounding fuel cells. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 |
From: SourceForge.net <no...@so...> - 2008-05-14 20:13:48
|
Feature Requests item #1933724, was opened at 2008-04-03 15:05 Message generated for change (Comment added) made by starseeker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Raytrace Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Marianne Kunkel (pantano) Assigned to: Nobody/Anonymous (nobody) Summary: Need NIRT to report target gaps (void spaces) Initial Comment: Would like an option for NIRT to explicitly report the xyz of beginning of a target gap (void space in the geometry) and length of that target gap for all target gaps encountered on the shotline. Reason: MUVES-S2 uses an algorithm, called airgap, to determine probability of sustained fire for API (armor piercing incendiary) threats against fuel systems in aircraft. One of the factors in predicting aircraft fires is the length of the target gap between where the munition "functions" (releasing incendiary) and where the munition encounters fuel (or other flammable fluid). Efforts to debug MUVES results would be enhanced if NIRT could automatically report target gaps to the user. This would also help target describers validate target descriptions of fuel systems and the target gaps(called aircraft dry bays) surrounding fuel cells. ---------------------------------------------------------------------- >Comment By: Cliff Yapp (starseeker) Date: 2008-05-14 15:13 Message: Logged In: YES user_id=11463 Originator: NO Added to nirt as a reporting option as of svn commit #31108 - see updated man page. Should be in next stable release (7.12.4+) ---------------------------------------------------------------------- Comment By: Cliff Yapp (starseeker) Date: 2008-05-14 15:13 Message: Logged In: YES user_id=11463 Originator: NO This feature request is now implemented and should be available with the next release, thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 |
From: SourceForge.net <no...@so...> - 2008-06-26 23:35:03
|
Feature Requests item #1933724, was opened at 2008-04-03 20:05 Message generated for change (Settings changed) made by brlcad You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Raytrace >Group: Minor Effort Status: Closed Resolution: Fixed >Priority: 7 Private: No Submitted By: Marianne Kunkel (pantano) >Assigned to: Cliff Yapp (starseeker) Summary: Need NIRT to report target gaps (void spaces) Initial Comment: Would like an option for NIRT to explicitly report the xyz of beginning of a target gap (void space in the geometry) and length of that target gap for all target gaps encountered on the shotline. Reason: MUVES-S2 uses an algorithm, called airgap, to determine probability of sustained fire for API (armor piercing incendiary) threats against fuel systems in aircraft. One of the factors in predicting aircraft fires is the length of the target gap between where the munition "functions" (releasing incendiary) and where the munition encounters fuel (or other flammable fluid). Efforts to debug MUVES results would be enhanced if NIRT could automatically report target gaps to the user. This would also help target describers validate target descriptions of fuel systems and the target gaps(called aircraft dry bays) surrounding fuel cells. ---------------------------------------------------------------------- Comment By: Cliff Yapp (starseeker) Date: 2008-05-14 20:13 Message: Logged In: YES user_id=11463 Originator: NO Added to nirt as a reporting option as of svn commit #31108 - see updated man page. Should be in next stable release (7.12.4+) ---------------------------------------------------------------------- Comment By: Cliff Yapp (starseeker) Date: 2008-05-14 20:13 Message: Logged In: YES user_id=11463 Originator: NO This feature request is now implemented and should be available with the next release, thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640805&aid=1933724&group_id=105292 |