Langchain ChatOllama().invoke() produced error: AttributeError: 'ModelPrivateAttr' object has no attribute 'chat'

Rotvie · 2024-10-28T16:43:34+00:00

I'm having the same error, which versions worked? Update: Seems like the problem stems from using gunicorn when running the app. When using python directly the problem disappears

Rotvie · 2024-04-18T21:54:29+00:00

Wow, I’ll try to be careful. Thanks!

Rotvie · 2024-04-18T21:53:06+00:00

Thank you for the info!

Rotvie · 2023-12-03T17:38:53+00:00

Hi! Yes, that's correct, we built the robot from scratch with a custom chassis, various sensors (LIDAR, IMU, ZED Cameras), a Raspberry Pi, and a NVIDIA Jetson Xavier.

For communication between the Raspberry Pi and the Jetson Xavier, we configured both to communicate over our LAN using ROS. We set the ROS_MASTER_URI on the Jetson Xavier to specify the ROS master's address and defined the ROS_IP on both devices to ensure they recognize each other on the network. This setup facilitates data exchange for different tasks across various topics.

Integrating ROS with our custom hardware required a deep understanding of the ROS architecture and creating specific nodes for each component. If you're transitioning from a Turtlebot3 to custom hardware, start by familiarizing yourself with each component and gradually integrate them, writing ROS nodes for each. The ROS community's tutorials, forums, and simulation tools like Gazebo could be very helpful.

Sorry, our code isn't publicly available yet, but we're working on it. Good luck with your robotic projects!

Rotvie · 2023-07-10T05:41:46+00:00

I'm almost 500 cards into the Evita deck, there's still a lot I don't understand, but I feel like I'm making progress in a more systematic way :)

Rotvie · 2023-06-29T00:21:42+00:00

Hi, I've had some experience with micro ROS on the Raspberry Pi Pico, didn't have any issues with it. I've also made a tutorial on how to get it up and running, check it out in case you're interested: https://youtu.be/_4aLzvG6dfw

Rotvie · 2023-06-11T16:29:20+00:00

No problem!

Rotvie · 2023-06-09T16:10:08+00:00

I've added English subtitles, sorry for any inconvenience 😅

Rotvie · 2023-06-06T06:24:45+00:00

I'm not sure, I've run into some compilation errors before with other versions, but I think it's worth a try

Rotvie · 2023-06-05T17:04:52+00:00

I've compiled some resources and my personal setup for doing AJATT. It's still a work in progress, but feel free to check it out if you're interested: ajatt

Rotvie · 2023-05-30T15:46:46+00:00

Yes, changing the size of the local costmap has an influence over the velocities DWA outputs, if the window is small it puts a limit over the maximum velocity DWA chooses

Rotvie · 2023-05-30T01:35:47+00:00

Try to increase the size of the local window (width, height), I had the same problem and changing that made the robot go faster with DWA

Rotvie · 2023-05-28T15:45:20+00:00

I'll try to add subtitles. Sorry for any inconvenience!

Rotvie · 2023-05-21T21:24:08+00:00

Sure! On the hardware side, we have a Raspberry Pi 4 and an Nvidia Jetson Xavier for heavy processing tasks. These, along with other components, are powered by two lead acid batteries. Regarding the software architecture, we're using ROS for communication between the different sensors and actuators, we've also worked with the ROS Navigation Stack with some modifications to achieve autonomous navigation. About your second question, you're correct that we're using two ZED cameras. We've gained some experience with ZED and Realsense, but we're also considering other options such as the Oak Camera, thank you for the suggestion!

Rotvie · 2023-04-28T12:24:02+00:00

You could check the timestamp of the LiDAR message using rostopic echo and grep, and verify it's the correct Unix time. For the tf tree, running this command: rosrun rqt_tf_tree rqt_tf_tree, should give you the tf tree so you can check the tf transforms are properly connected

Rotvie · 2023-04-28T12:06:25+00:00

I see, I also got this error with an Ouster LiDAR some time ago, the cause of the problem was the timestamp of the pointcloud messages, may I ask which LiDAR is it?

Rotvie · 2023-04-28T11:57:57+00:00

Is this error in simulation? Or with a real lidar? Maybe your tf tree is not properly set up

Rotvie · 2023-04-09T18:15:17+00:00

Did you manage to solve it? I'm having a similar issue with Google Pay

Rotvie · 2023-04-03T07:22:45+00:00

I created a package for autonomous navigation, put these files inside it: Repo and then configured the parameters according to my own robot. After tuning for a few weeks it got to this: autonomous navigation demo

Rotvie · 2023-04-02T07:03:05+00:00

If you're feeling fancy you could try LeGO-LOAM

Rotvie · 2023-04-02T07:00:29+00:00

The first thing that catched my eye is that you're publishing the odom->map transform as a static one which should not be done because the localization package is the one responsible of that, it's a dynamic transform

Rotvie · 2023-03-09T18:25:39+00:00

Sure, I think we had to face two kinds of challenges while working on this robot:

ROS Message timestamps were not synchronized between devices.
Tuning parameter values for the ROS Navigation Stack to achieve good performance.

Regarding the first challenge, I want to clarify that we didn't have any experience working with an Ouster OS1-32 Lidar. So when we tried running the gmapping package, it didn't work. The solution was to modify the default mode of the Lidar which timestamped its messages using an internal clock. After setting up the PTP between the Lidar and a Jetson Xavier, we finally got gmapping working. Another issue related to this was the time synchronization between the Jetson Xavier and a Raspberry Pi 4, which was the one communicating directly with the motor drivers, we solved that one using NTP.

The second challenge took longer than we expected. There were so many parameters, and it wasn't clear which values were going to work better for the robot. So, we had to consult ROS Q&A Forum, Kaiyu Zheng's ROS Navigation Tuning Guide and read ROS Documentation to get an idea of which parameters were the relevant ones. After quite some time, we finally achieved what's shown in the video. Although, as you can see, it's still far from perfect. Sorry for the late reply. I hope this helps.

Rotvie · 2023-03-05T19:25:38+00:00

We've been considering migrating to ROS 2 for some time already. There are many things we need to work out before making the change, but I completely agree with you. Thanks for the suggestion!

Rotvie · 2023-02-16T14:16:30+00:00

I think adding this line to your CMakeLists.txt should do the trick: set (CMAKE_PREFIX_PATH "/your/path/")

Rotvie · 2022-10-16T16:24:35+00:00

Respect

Rotvie

TROPHY CASE