hi, I’m new to rasa and have some questions:
- is it possible to use rasa without having a server application (I’m writing an app which is a copilot for flight simulator and I want to use rasa as the backbone of my copilot) I want to use actions to set plain’s stuff (things like heading bug, altitute bug etc) and, i don’t need the http server because flight simulator has it’s own sdk and I’m going to use that. also, should I instanciate an Agent by my own?
- in real world, pilots and copilots do a series of checklists which is different for each airline now, I want to read them from a file (like preflight.txt) and complete them with rasa. the thing that i did was to declare an intent called do_checklist with checklist_name as entity. now, I think that i should use form policy to do that. is that correct? or there is another way
- in the checklists, some of the items need to be saved (may I use slots)? like takeoff speeds etc
- how would I limit an entity to something? for example, how can i limit heading from 1 to 360? for example, set heading 360 correct while set heading 400 is not
- how can i pause/resume a checklist? should I use events or something else for it? and how can i call that from python
- I want to immplement departure briefing. how would i do tthat? in the departure briefing, captain gives information regarding flight information to copilot. this is an example: captain: “are you ready for the departure briefing?” copilot: “affirmative” captain: “I’m making a high-density altitude takeoff in a fairly heavy airplane in a high traffic area. I’ve confirmed all checklist items are complete. I have a slight crosswind from the right. I’ll attain about 23 inches manifold pressure at full throttle and lean to approximately 1300°F EGT. I should be at 60 knots at five stripes down the runway and lift off about 11 stripes down the runway. At liftoff I’ll raise the nose to 10° up for VXME at first, then 5° up for VYSE. I’ll delay gear retraction until I confirm a sustained positive rate of climb. After reaching 400 AGL, turn southeast toward the VOR and climb to 11,000 feet unless directed otherwise. On course is southeast from the VOR once reaching 11,000 feet. Alternately, if conditions permit, request ATC for a visual climb, assuming obstacle clearance responsibility myself. If granted, turn left toward my first fix while climbing to 11,000 feet. The hold at SAF has an inbound course of 334° and an outbound heading of 154°. Hold entry will be by teardrop with an initial heading of 120°. in case of emergency, If the speed is above 80 knots, I will abort the takeoff. otherwise we will climb to about 7500 fit then request for emergency landing. any questions?” copilot: “no questions” captain: “departure briefing completed” this was a simple example of a departure briefing, but it has a lot of information on it. how would I give these to rasa? should i store these in slots as well? or, how can i process this? notice that the departure/landing briefing is different for each flight and people announce it differently.
- and, how can I implement a custom policy for pytorch? since I want to turn the application into ann executable and give that to my friends. thanks