2.6 PAL demos (speedruns)


drones

Its the first example of setting up the Workshop (UI).

  • It took a long time to get right (several days). And its usually the last thing you setup for an app. If you made a mistake earlier in the pipeline, ontology, functions, etc then things just dont work in the workshop. And its not easy (for a beginner) to figure out why.
  • The diagram shows that are basically 2 parts that dont depend on each other.
    • The bottom widget response takes the top widget input and uses an LLM to answer the question with the RAG input.
    • The left and right widgets do the complicated part
      • Left widget takes the query text and compares against the embedding values in the “TT2 Chunk VVV” object type. It outputs to variable “Relevant Chunks VVV” the top 9 matching embeddings.
      • Right widget takes the relevant chunks and inputs to the Vertex template for display.
  • What this means is you could have done this demo from start (pipeline) to finish (UI) in 3 parts.
    • First LLM (top and bottom widgets).
    • Then display the nearest embedding neighbors (left widget).
    • Finally build the template and add to the right widget.
  • That would make it easier to handle all the complexity and not get stuck.
  • But best of all would be to have this as an example. You install 2 working example instance. Use one as a reference and slowly rebuild parts of the other.

drones


26.0811 (0725, 26.0713)