-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Test Case]: Alignment Curves #22
base: develop
Are you sure you want to change the base?
[Test Case]: Alignment Curves #22
Conversation
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.
Some suggestions, waiting for further content.
- Linear | ||
|
||
The valid geometry segment types for vertical: | ||
- Arc |
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.
- Arc | |
- Circular Arc |
More specific more better.
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.
Leaving as Arc for now. Has to be changed in the partial template name also.
Probably wrong placement of these though.
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.
Waiting for further input :)
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.
We need something under Dataset as well at some point.
- *IfcAxis2PlacementLinear* | ||
- *IfcAxis2Placement2D* | ||
- *IfcAxis2Placement3D* | ||
- *IfcCircle* |
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.
How do we handle the cases in ALIN where we have no requirements for geometry at all (only layout)? Can we split this in two (with/without geometry)?
|
||
- *Alignment Layout* | ||
- *Alignment Geometry* | ||
- *Alignment Geometry Gradient* |
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.
Same comment as above. Split in two TIs (with/without geometry)?
<details><summary>Semantic Usages, Constraints & Logic</summary> | ||
|
||
The following itemised Usages, Constraints & Logic are normative entries within the AbRV MVD and MUST be satisfied to meet the defined validation criteria | ||
|
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.
To me it's a little unclear what exactly to write in this section and what to put in validation criteria below => Discussion!
|
||
## Validation criteria | ||
:zap: For this test case to be considered passed **all capabilities** listed in this section shall be verified, with no exception. :zap: | ||
|
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 guess this needs to be added...
Summary
Outline of the content and tasks addressed by this pull request, dont forget to link the relevent issue(s)
Purpose
Please mark the relevent tasks that this pull request creates or updates:
Resolves #4
Adding test instruction first stage documentation for
[Test Case]: Alignment Curves
Test Cases