You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: metro-ai-suite/metro-vision-ai-app-recipe/docs/user-guide/tutorial-4.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,6 +212,9 @@ Here are the example prompts that we used:
212
212
213
213
-**Prompt for Vehicle Position Extractor**: The code output from co-pilot after vibe coding with this prompt is used in step #7.7 below
214
214
- Here is the metadata output from DL Streamer Pipeline Server (Video Analytics pipeline) that does object detection. [PASTE METADATA HERE]. Provide a node red function that parses bounding box coordinates (x, y, w, h format) to calculate centroids, only include objects that are vehicles and return output message with vehicle positions.
215
+
> Note: After completing step #7.6 and starting the pipeline using the curl command, open the Node-RED debug panel on the right (bug icon). Select the Vehicle Data Monitor debug node from the drop down in the debug panel to view the metadata, which is used in the prompt to generate Extract Vehicle Positions.
### **Appendix: Fine-tuning Node-RED Functions with Claude Sonnet 4.5**
795
+
796
+
When developing Node-RED function nodes for advanced analytics, you can leverage prompt engineering with Claude Sonnet 4.5 to iteratively refine your code. Here’s how you can approach fine-tuning:
0 commit comments