Skip to content
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

Extension of Mission definition #562

Closed
HHOPs opened this issue Aug 30, 2018 · 3 comments
Closed

Extension of Mission definition #562

HHOPs opened this issue Aug 30, 2018 · 3 comments

Comments

@HHOPs
Copy link

HHOPs commented Aug 30, 2018

It would be helpful to integrate "events" within future versions of the mission definition:

  • Mass dropping (w. reference to mass properties / weight and balance) - eventually also referencing a modified aerodynamics performance map

  • Air refuelling (w. reference to mass propertie / weight and balance or simplified with FF etc.)

  • De-tanking strategy / sequence (w. reference to mass propertie / weight and balance etc.)

  • Failure states (OEO/OEI, certain control elements inop, declare emergency within a segment etc.)

@DLR-LY
Copy link
Collaborator

DLR-LY commented Nov 22, 2018

Could you provide a schema for your proposal?

I recommend using the Eclipse editor (Eclipse IDE for Java Developers) to simply implement your ideas into the current CPACS schema. Since I haven't finished my tutorial yet, please find a short description in the following. Don't worry about the correct implementation, I will take care of that. But in this way we have a better basis for discussion.

  1. Download and install Eclipse.

  2. Use Open File to load the cpacs_schema.xsd file from the schema folder in your CPACS directory.

  3. Go to the Design view. Here you have a graphical overview of the cpacs structure. Click on "cpacs : cpacsType" in the list on the right. This opens the cpacsType.
    eclipse1
    (how wonderful Paint still is...)

  4. In the cpacs type open the missionsDefinitionsType:
    eclipse2

  5. Find the place where you want to add your elements like this:
    eclipse3

  6. Choose the multiplicity:
    eclipse4

  7. Finally, define your new type: Right click on the "events" element -> new Type -> "eventsType"
    eclipse5

  8. Inherit this new type from "complexBaseType".

  9. Right mouse click on "eventsType" -> "add Element" -> rename "NewElement" to "event"

  10. Set Multiplicity of "event" to "[1..*]" and use "Set Type" to define a new complex Type "eventType".

  11. Use "add Attribute " to add the "uID" attribute.

  12. Use again "add Element" to define new elements in the event Type. Changing the type from "string" to a complex type, e.g. "airRefuellingType" allows you to add again new child elements.

  13. Finally, by clicking on the three dots you may change the sequence type from "sequence" to "all" or "choice".
    eclipse7

  14. Design your xsd-structure, zip the file and drag&drop into the comment area to upload the file to this issue discussion.

I hope this will help to set up a schema.

@HHOPs
Copy link
Author

HHOPs commented Nov 23, 2018 via email

@MarAlder
Copy link
Collaborator

MarAlder commented Jul 7, 2021

closed by #716.

@MarAlder MarAlder closed this as completed Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants