neroexecutive.blogg.se

Interact scratchpad
Interact scratchpad











interact scratchpad
  1. INTERACT SCRATCHPAD FULL
  2. INTERACT SCRATCHPAD CODE
  3. INTERACT SCRATCHPAD SIMULATOR

The scratchpad is also where the FMC places messages. As an example, you can use the keyboard to enter the name of a waypoint “ YOW” and enter it into the LEGS page to change aircraft navigation. From here they can be either cleared or line selected up into one of the lines of the CDU display above. Any text entered in via the keyboard or line selected down from the higher lines of the CDU end up in the scratchpad. The scratchpad itself is the incongruous name given to the bottom line of the CDU. They are not (directly) a part of Boeing’s design intent for the alerting system of the aircraft – that said, some of them do come with an EICAS alert FMC MESSAGE – many do not though. It is a one line display that the FMC uses in order to pass a message onto the crew. We areseeing this in the sim and in the aircraft – occaisionally to the detriment of the operation of the aircraft.įMC (Flight Management Computer) scratchpad messages are generated at the bottom of the screen built into the FMC CDU (Computer Display Unit).

INTERACT SCRATCHPAD SIMULATOR

Most particularly around the habit that some crew develop – usually during transition simulator training when many spurious messages are generated and often cleared without real understanding of their meaning). NotebookDocument is returned from interactive.There has been some discussion recently around FMC scratchpad messages, their role in flight deck alerting, and an appropriate crew response. Interactive window needs to be passed a controller ID at creation to pick up the right controller (alternative is lectKernel or similar after the window is created, but we’ve discussed this and decided not to do it).

INTERACT SCRATCHPAD CODE

  • Our code currently also starts a new kernel for each new NotebookDocument in kernelProvider.getOrCreate.
  • Controllers can only create execution tasks for the NotebookDocument that they are currently associated with in VS Code.
  • in order to create the notebook cell execution task controller is passed into IKernel constructor and then passed all the way down through the constructors of KernelExecution, CellExecutionQueue, CellExecution etc.
  • Our code currently assumes a 1-1 relationship between a VS Code NotebookController and our internal IKernel objects, i.e.
  • Currently vscode.NotebookControllers are per-notebookType, so to get our kernels to show up for interactive windows, each of our kernels is registered twice with VS Code–once for the jupyter-notebook notebookType and once for the interactive notebookType.
  • to be reused for an interactive controller that is selected for a given interactive NotebookDocument.
  • an IKernel that is currently mapped to a jupyter-notebook controller which has been selected for a given jupyter-notebook NotebookDocument.
  • Summary: Jupyter extension needs to refactor our VSCodeNotebookController wrapper, IKernel, and the cell execution codepath to allow.
  • Introduce keybinding or similar to copy code (otherwise user has to move mouse literally the entire span of the screen).
  • INTERACT SCRATCHPAD FULL

    Should the scratchpad contain just the one cell (fully matching behavior) or be a full interactive window?.Should users be able to start multiple interactive consoles? Original prototype has scratchpad singleton.Should the interactive window immediately receive focus when created?.Context keys to hide interactive window specific functionality.Sys info cell to indicate the notebook association.

    interact scratchpad interact scratchpad

  • Command contributed to interactive/cell/title to paste code back into notebook.
  • Command contributed to notebook/cell/title to open interactive window connected to same kernel.
  • “…have an ability to launch an IPython shell (within VS Code) which is binded to the kernel of a specific notebook (so all objects defined in the notebook are accessible there etc.)…”.
  • The main usecase is to be able to work interactively based on the state of a notebook without having to tinker with the notebook itself.”
  • “…create interactive Python consoles connected to specific notebook kernels.
  • “…interactive command line that is connected to a jupyter notebook…”.
  • “I add some cells to try something out and I don’t want to lose them, but I don’t want them in my ‘main’ notebook.”.












  • Interact scratchpad