I'm trying to publish a CameraInfo message so that I can (eventually) use image_proc. I tried to write the subscriber/publisher from scratch and ran into the issue with filling in entries in the D matrix of the CameraInfo message (segfaults caused by allocation issues).
I looked around and found the camera_info_manager package but I can't figure out how to use it. I've tried to copy/paste what I could from the [camera1394 drivers](https://github.com/ros-drivers/camera1394/blob/master/src/nodes/driver1394.cpp) recommended by [this](http://answers.ros.org/question/11361/how-to-publish-sensor_msgscamerainfo-messages/) thread but I can't figure out how to initialize it--the references for the initialization are missing.
Update: I've gotten the problem down to a camera URL issue. I run the code with a rosbag publishing images and get an error from camera_info_manager reading
Camera calibration file /home/rnl/.ros/camera_info/camtest1.yaml not found.
Update 2: It all works now, camera_info_manager was not reading properly from the .yaml. Whoever had installed the package on this machine had downloaded it from a bad source.
code here
//includes and whatnot
class publishCameraInfo
{
public:
publishCameraInfo()
{
//Topic you want to publish
image_pub_ = n_.advertise("snap_cam_camInfo/CameraInfo", 1);
//Topic you want to subscribe
sub_ = n_.subscribe("snap_cam_highres_publisher/image", 1, &publishCameraInfo::callback, this);
}
void callback(const sensor_msgs::Image& imgmsg)
{
const std::string camname="camtest1";
const std::string camurl="file://~/.ros/camera_info/camtest1.yaml";
camera_info_manager::CameraInfoManager caminfo(n_, camname,camurl);
sensor_msgs::CameraInfo ci;
ci=caminfo.getCameraInfo();
ci.header.stamp = imgmsg.header.stamp;
ci.header.frame_id = imgmsg.header.frame_id;
image_pub_.publish(imgmsg, ci);
}
private:
ros::NodeHandle n_;
ros::Publisher image_pub_;
ros::Subscriber sub_;
};//End of class
int main(int argc, char **argv)
{
ros::init(argc, argv, "publishCameraInfo");
publishCameraInfo cameraPubObject;
ros::spin();
return 0;
}
↧
CameraInfo publisher can't find .yaml file
↧
RGBD colour balance?
I am using Astra Pro with usb_cam. I calibrate the hue using v4lcup. Images are pulled using v4l driver. When I finish calibration the images looks fine in rviz. However, when I pass images from usb_cam to image_proc the image_rect_color looks very distorted in rviz.
How do I balance the colour after image_proc?
Thanks.
↧
↧
Probleme with parameter queue_size in image_proc node
Hello everyone,
I try to change the size of the message queue in image_proc by raising the parameter ~queue_size in a roslaunch file:
.
.
.
The parameter is raising correctly, it appears in rosparm list under the name : /camera_pi/image_proc/queue_size (seem correct to me ?). But this as no effect on the queue size of the node who remaining at the default size (5).
Any idea ?
Thanks
↧
rosbag conversion
I want to convert a image Mat type CV_32FC1 containing a depth map back into a Mat CV_16UC1 from which it originally came. Does the code below do this? Do I have normailze it? ( 1/255.0)? I hope this question is acceptable here if not I will l post else where.
cv::Mat inputData = cv::Mat(cv::Size(640, 480), CV_16UC1);
inputData.convertTo(cv_ptrD->image, CV_16UC1);
↧
LibViso2 process has died
I am trying the libviso2 package for visual odometry in ROS jade.I am getting this error
usb_cam/image_proc-1] process has died [pid 16445, exit code -11
Is it because the this package is available for ROS distros upto indigo and not Jade?
This is the the launch file
`
↧
↧
image_proc not publishing image_rect data after synchronizing camera_info
I have a camera driver without the camera_info topic. I am publishing this topic separately and synchronizing them with all the image_proc topics. I am getting data in image_mono and image_color but not in image_rect or image_rect_color topics.
I am still getting a warning for non-synchronization.
[ WARN] [1512057285.359548566]: [image_transport] Topics '/camera/0/0/image_color' and '/camera/0/0/camera_info' do not appear to be synchronized. In the last 10s:
Image messages received: 297
CameraInfo messages received: 300
Synchronized pairs: 0
Below is the sync node.
#include
#include
#include
#include
#include
#include
#include
using namespace sensor_msgs;
using namespace message_filters;
ros::Publisher image_raw_pub;
ros::Publisher image_mono_pub;
ros::Publisher image_color_pub;
ros::Publisher image_rect_pub;
ros::Publisher image_rect_color_pub;
ros::Publisher camera_info_pub;
void callback(const Image::ConstPtr& image1, const Image::ConstPtr& image2, const Image::ConstPtr& image3, const Image::ConstPtr& image4, const Image::ConstPtr& image5, const CameraInfo::ConstPtr& info)
{
// Solve all of perception here...
ROS_INFO("Sync_Callback");
image_raw_pub.publish(image1);
image_mono_pub.publish(image2);
image_color_pub.publish(image3);
image_rect_pub.publish(image4);
image_rect_color_pub.publish(image5);
camera_info_pub.publish(info);
}
int main(int argc, char** argv)
{
ros::init(argc, argv, "camera_info_node");
std::string img_raw_topic = "/camera/0/0/image_raw";
std::string img_mono_topic = "/camera/0/0/image_mono";
std::string img_color_topic = "/camera/0/0/image_color";
std::string img_rect_topic = "/camera/0/0/image_rect";
std::string img_rect_color_topic = "/camera/0/0/image_rect_color";
std::string camera_info_topic = "/camera/0/0/camera_info";
ros::NodeHandle nh;
message_filters::Subscriber image_raw_sub(nh, img_raw_topic, 100);
message_filters::Subscriber image_mono_sub(nh, img_mono_topic, 100);
message_filters::Subscriber image_color_sub(nh, img_color_topic, 100);
message_filters::Subscriber image_rect_sub(nh, img_rect_topic, 100);
message_filters::Subscriber image_rect_color_sub(nh, img_rect_color_topic, 100);
message_filters::Subscriber camera_info_sub(nh, camera_info_topic, 100);
image_raw_pub = nh.advertise(img_raw_topic, 1000);
image_mono_pub = nh.advertise(img_mono_topic, 1000);
image_color_pub = nh.advertise(img_color_topic, 1000);
image_rect_pub = nh.advertise(img_rect_topic, 1000);
image_rect_color_pub = nh.advertise(img_rect_color_topic, 1000);
camera_info_pub = nh.advertise(camera_info_topic, 1000);
typedef sync_policies::ApproximateTime MySyncPolicy;
// ApproximateTime takes a queue size as its constructor argument, hence MySyncPolicy(10)
Synchronizer sync(MySyncPolicy(10), image_raw_sub, image_mono_sub, image_color_sub, image_rect_sub, image_rect_color_sub, camera_info_sub);
sync.registerCallback(boost::bind(&callback, _1, _2, _3, _4, _5, _6));
ros::spin();
return 0;
}
**EDIT:**
On synchronizing only image_raw, image_mono and camera_info, the warning message is removed.
However, the image_rect and image_rect_color still does not publish anything.
Note: The two topics are being subscribed but no messages are being published.
↧
Why do nodelets sometimes not start
I have a standard camera pipeline set up with nodelets:
pointgrey_camera_driver -> image_proc (debayer/rectify)
It's running inside of a nodelet manager called bumblebee2_nodelet_manager
Sometimes, it starts fine. Sometimes, it crashes horribly. All of the log files are empty.
Sample of working stdout:
... logging to /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/roslaunch-alicia-huskeys-562.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is (lessthan)1GB.
started roslaunch server http://192.168.1.11:36736/
SUMMARY
========
PARAMETERS
* /bumblebee2/pointgrey_camera_driver/camera_info_url: file:///home/admi...
* /bumblebee2/pointgrey_camera_driver/first_namespace: left
* /bumblebee2/pointgrey_camera_driver/format7_color_coding: raw16
* /bumblebee2/pointgrey_camera_driver/frame_id: bumblebee
* /bumblebee2/pointgrey_camera_driver/frame_rate: 24
* /bumblebee2/pointgrey_camera_driver/second_info_url: file:///home/admi...
* /bumblebee2/pointgrey_camera_driver/second_namespace: right
* /bumblebee2/pointgrey_camera_driver/serial: 8511553
* /rosdistro: indigo
* /rosversion: 1.11.21
NODES
/bumblebee2/
bumblebee2_nodelet_manager (nodelet/nodelet)
debayer_left (nodelet/nodelet)
debayer_right (nodelet/nodelet)
pointgrey_camera_driver (nodelet/nodelet)
rectify_color_left (nodelet/nodelet)
rectify_color_right (nodelet/nodelet)
rectify_mono_left (nodelet/nodelet)
rectify_mono_right (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[bumblebee2/bumblebee2_nodelet_manager-1]: started with pid [581]
process[bumblebee2/pointgrey_camera_driver-2]: started with pid [582]
process[bumblebee2/debayer_left-3]: started with pid [583]
process[bumblebee2/debayer_right-4]: started with pid [584]
process[bumblebee2/rectify_mono_left-5]: started with pid [591]
process[bumblebee2/rectify_mono_right-6]: started with pid [599]
process[bumblebee2/rectify_color_left-7]: started with pid [607]
process[bumblebee2/rectify_color_right-8]: started with pid [624]
Sample of crashing stdout:
... logging to /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/roslaunch-alicia-huskeys-5127.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is (lessthan)1GB.
started roslaunch server http://192.168.1.11:46324/
SUMMARY
========
PARAMETERS
* /bumblebee2/pointgrey_camera_driver/camera_info_url: file:///home/admi...
* /bumblebee2/pointgrey_camera_driver/first_namespace: left
* /bumblebee2/pointgrey_camera_driver/format7_color_coding: raw16
* /bumblebee2/pointgrey_camera_driver/frame_id: bumblebee
* /bumblebee2/pointgrey_camera_driver/frame_rate: 24
* /bumblebee2/pointgrey_camera_driver/second_info_url: file:///home/admi...
* /bumblebee2/pointgrey_camera_driver/second_namespace: right
* /bumblebee2/pointgrey_camera_driver/serial: 8511553
* /rosdistro: indigo
* /rosversion: 1.11.21
NODES
/bumblebee2/
bumblebee2_nodelet_manager (nodelet/nodelet)
debayer_left (nodelet/nodelet)
debayer_right (nodelet/nodelet)
pointgrey_camera_driver (nodelet/nodelet)
rectify_color_left (nodelet/nodelet)
rectify_color_right (nodelet/nodelet)
rectify_mono_left (nodelet/nodelet)
rectify_mono_right (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[bumblebee2/bumblebee2_nodelet_manager-1]: started with pid [5148]
process[bumblebee2/pointgrey_camera_driver-2]: started with pid [5149]
process[bumblebee2/debayer_left-3]: started with pid [5150]
process[bumblebee2/debayer_right-4]: started with pid [5151]
process[bumblebee2/rectify_mono_left-5]: started with pid [5157]
process[bumblebee2/rectify_mono_right-6]: started with pid [5170]
process[bumblebee2/rectify_color_left-7]: started with pid [5183]
process[bumblebee2/rectify_color_right-8]: started with pid [5196]
[FATAL] [1513803260.804449868]: Failed to load nodelet '/bumblebee2/pointgrey_camera_driver` of type `pointgrey_camera_driver/PointGreyStereoCameraNodelet` to manager `bumblebee2_nodelet_manager'
[FATAL] [1513803260.804448840]: Failed to load nodelet '/bumblebee2/rectify_color_right` of type `image_proc/rectify` to manager `bumblebee2_nodelet_manager'
[FATAL] [1513803260.804454183]: Failed to load nodelet '/bumblebee2/debayer_right` of type `image_proc/debayer` to manager `bumblebee2_nodelet_manager'
[FATAL] [1513803260.804547296]: Failed to load nodelet '/bumblebee2/rectify_mono_left` of type `image_proc/rectify` to manager `bumblebee2_nodelet_manager'
[FATAL] [1513803260.807931869]: Failed to load nodelet '/bumblebee2/debayer_left` of type `image_proc/debayer` to manager `bumblebee2_nodelet_manager'
[bumblebee2/bumblebee2_nodelet_manager-1] process has died [pid 5148, exit code -11, cmd /opt/ros/indigo/lib/nodelet/nodelet manager __name:=bumblebee2_nodelet_manager __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-bumblebee2_nodelet_manager-1.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-bumblebee2_nodelet_manager-1*.log
[bumblebee2/pointgrey_camera_driver-2] process has died [pid 5149, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load pointgrey_camera_driver/PointGreyStereoCameraNodelet bumblebee2_nodelet_manager --no-bond __name:=pointgrey_camera_driver __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-pointgrey_camera_driver-2.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-pointgrey_camera_driver-2*.log
[bumblebee2/debayer_left-3] process has died [pid 5150, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load image_proc/debayer bumblebee2_nodelet_manager --no-bond image_raw:=left/image_raw image_mono:=left/image_mono image_color:=left/image_color __name:=debayer_left __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-debayer_left-3.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-debayer_left-3*.log
[bumblebee2/debayer_right-4] process has died [pid 5151, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load image_proc/debayer bumblebee2_nodelet_manager --no-bond image_raw:=right/image_raw image_mono:=right/image_mono image_color:=right/image_color __name:=debayer_right __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-debayer_right-4.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-debayer_right-4*.log
[bumblebee2/rectify_mono_left-5] process has died [pid 5157, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load image_proc/rectify bumblebee2_nodelet_manager --no-bond image_mono:=left/image_mono camera_info:=left/camera_info image_rect:=left/image_rect __name:=rectify_mono_left __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-rectify_mono_left-5.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-rectify_mono_left-5*.log
[bumblebee2/rectify_color_right-8] process has died [pid 5196, exit code 255, cmd /opt/ros/indigo/lib/nodelet/nodelet load image_proc/rectify bumblebee2_nodelet_manager --no-bond image_mono:=right/image_color camera_info:=right/camera_info image_rect:=right/image_rect_color __name:=rectify_color_right __log:=/home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-rectify_color_right-8.log].
log file: /home/administrator/.ros/log/37aadb7a-e5c6-11e7-9ea0-003018cfd00f/bumblebee2-rectify_color_right-8*.log
↧
Single image pair processing with stereo_image_proc
Now, stereo image proc works with a stream of input L and R images and outputs a stream as well. How do I make it just give me all the outputs (rectified images, disparity map, point cloud,..) for just a single image pair input?
↧
cv_bridge tutorial example not compiling in ROS Kinetic and Ubuntu 16.04
Hi,
I am trying to run the full example in the cv_bridge tutorial at http://wiki.ros.org/cv_bridge/Tutorials/UsingCvBridgeToConvertBetweenROSImagesAndOpenCVImages . I am having serious trouble compiling the node.
I get the following undefined reference errors for opencv functions as follows:
CMakeFiles/c_test_node.dir/src/c_test_node.cpp.o: In function `ImageConverter::ImageConverter()':
c_test_node.cpp:(.text._ZN14ImageConverterC2Ev[_ZN14ImageConverterC5Ev]+0x3f1): undefined reference to `cv::namedWindow(cv::String const&, int)'
CMakeFiles/c_test_node.dir/src/c_test_node.cpp.o: In function `ImageConverter::imageCb(boost::shared_ptr> const> const&)':
c_test_node.cpp:(.text._ZN14ImageConverter7imageCbERKN5boost10shared_ptrIKN11sensor_msgs6Image_ISaIvEEEEE[_ZN14ImageConverter7imageCbERKN5boost10shared_ptrIKN11sensor_msgs6Image_ISaIvEEEEE]+0x1bd): undefined reference to `cv::imshow(cv::String const&, cv::_InputArray const&)'
c_test_node.cpp:(.text._ZN14ImageConverter7imageCbERKN5boost10shared_ptrIKN11sensor_msgs6Image_ISaIvEEEEE[_ZN14ImageConverter7imageCbERKN5boost10shared_ptrIKN11sensor_msgs6Image_ISaIvEEEEE]+0x1e2): undefined reference to `cv::waitKey(int)'
collect2: error: ld returned 1 exit status
c_test/CMakeFiles/c_test_node.dir/build.make:132: recipe for target '/home/auv/c_test_ws/devel/lib/c_test/c_test_node' failed
make[2]: *** [/home/auv/c_test_ws/devel/lib/c_test/c_test_node] Error 1
CMakeFiles/Makefile2:1813: recipe for target 'c_test/CMakeFiles/c_test_node.dir/all' failed
make[1]: *** [c_test/CMakeFiles/c_test_node.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j8 -l8" failed
I have tried updating the include lines from:
#include
#include
to
#include
#include
However, I am not having luck with that either.
Any help or insight on this is very appreciated.
As per @Maarten 's suggestion, I am including my CMakeLists.txt here:
cmake_minimum_required(VERSION 2.8.3)
project(c_test)
find_package(catkin REQUIRED COMPONENTS
cv_bridge
image_transport
roscpp
sensor_msgs
std_msgs
tf
)
catkin_package(
CATKIN_DEPENDS cv_bridge image_transport roscpp sensor_msgs std_msgs
)
include_directories(
${catkin_INCLUDE_DIRS}
)
add_executable(c_test_node src/c_test_node.cpp)
target_link_libraries(c_test_node ${OpenCV_LIBS} ${catkin_LIBRARIES})
↧
↧
Rectification of single image.
Hi,
I have been looking at ROS calibration recently, and I came across the term "rectification" being used
for single images ( see [ROS image_proc](http://wiki.ros.org/image_proc) and [ROS image_geometry API for single camera](http://docs.ros.org/api/image_geometry/html/c++/classimage__geometry_1_1PinholeCameraModel.html#a3cb983f84f1993287247781a6bda39c2)).
**My question:**
From my understanding, the term rectification is used for stereo cameras/images. What does it mean for single cameras ? Is it the same is **un**-distortion of an image ?
↧
Why is image_raw better than image_rect_color ?
Hi,I am using Kinetic version.
I made monocular camera calibration of Logitech c930e by using [this tutorial of ROS](http://wiki.ros.org/camera_calibration/Tutorials/MonocularCalibration). Afterwards, I implemented rectification as described in [the document of image_proc](http://wiki.ros.org/image_proc). When I compare `image_raw` and `image_rect_color`, `image_raw` provides desired/rectified image (see the comparison image link below). Actual raw image is provided from `image_rect_color`. As I know, image_rect_color must be the rectified and desired result. All in all, I am confused about this issue and need an explanation. What am I doing wrong?
Comparison Image: https://drive.google.com/open?id=1eSQnJIIkmC9UVi04YxrQ6lpEiptPpPSV
↧
error while loading shared libraries: libopencv_calib3d3.so.3.2: cannot open shared object file
I see libopencv_calib3d.so, libopencv_calib3d.so.3.3, and libopencv_calib3d.so.3.3.1, but not what I need libopencv_calib3d.so.3.2 .
I have tried several methods, update ubuntu, create a 3.2 to 3.3 soft connection, and modify ld.so.conf.My OpenCV version is 3.1, ubuntu 16.04 and kinetic.
process[republish-1]: started with pid [3405]
process[camera/image_proc-2]: started with pid [3406]
/opt/ros/kinetic/lib/image_proc/image_proc: error while loading shared libraries: libopencv_calib3d3.so.3.2: cannot open shared object file: No such file or directory
[camera/image_proc-2] process has died [pid 3406, exit code 127, cmd /opt/ros/kinetic/lib/image_proc/image_proc _approximate_sync:=true image_raw:=image __name:=image_proc __log:=/home/burger/.ros/log/ccdd3c4e-9ba4-11e8-9c4b-000c29da7948/camera-image_proc-2.log].
log file: /home/burger/.ros/log/ccdd3c4e-9ba4-11e8-9c4b-000c29da7948/camera-image_proc-2*.log
↧
image_proc YUV422 Rectification messes up the colors
Hi,
I have an image topic `camera/image_color` which has images streaming with the encoding `sensor_msgs::image_encodings::YUV422`. When I see this image on rqt, I can see the image normally with correct colors.
I have the image rectification nodelet loaded with the following arguments
`--load image_proc/rectify image_proc_rectify_color image_mono:=image_color image_rect:=image_rect_color`.
It basically takes in `image_color` and spits out `image_rect_color`. The encoding of this rectified image is same as the input (YUV422) as per the header of the rectified image when I echo it. However, when I try to visualize this image on rqt, the image seems to be rectified, but the colors are weird.
Does anyone know what I might be missing? Does image rectify nodelet assumes RGB input and doesn't care about the encoding in the header of the input image? Is that why colors are wrong? Any help is appreciated.
Note: The YUV422 is the direct output from the camera sensor and I don't have `image_raw` or `image_mono` at all.
↧
↧
No rectified image output
Hello,
I am trying to generate a pointcloud from the depth camera of the robot pepper in conjunction with naoqi_driver, but I seem to get no output from the rectified image.
When calling rostopic list I see both topics, /naoqi_driver_node/camera/depth/image_raw and /naoqi_driver_node/camera/depth/image_rect but when using rostopic hz, only image_raw has an actual output, and I can't figure out why.
This is the code with which I'm trying to rectify the raw image data;
↧
[image_transport] Topics '/usb_cam/image_color' and '/usb_cam/camera_info' do not appear to be synchronized
please help me :(
$ rosrun image_transport republish compressed in:=usb_cam/image raw out:=usb_cam/image
$ ROS_NAMESPACE=usb_cam rosrun image_proc image_proc image_raw:=image _approximate_s=true _queue_size:=20
[ WARN] [1545066099.656226554]: [image_transport] Topics '/usb_cam/image_color' and '/usb_cam/camera_info' do not appear to be synchronized. In the last 10s:
Image messages received: 0
CameraInfo messages received: 45
Synchronized pairs: 0
↧
Cropping a raw camera image before it is rectified.
Hi,
After reading a lot of Q&A's on the topic, I still can't seem to crop an input image before rectifying it. I hope someone can help me. I'm runing KUbuntu 14.04 and ROS indigo
I can take a raw image, rectify it using the camera calibrator toolbox (e.g. using rosrun camera_calibration cameracalibrator.py -p circles -s 8x7 -q 0.02 image:=camera/image_raw&) and act upon the rectified image (view it etc). All fine, using the following :
roscore&
roslaunch uvc_camera webcam_calibrated.launch&
The launch file for uvc_camera is e.g.:
↧
image_proc needs one camera_info for every image !?
I'm developing some camera driver, and also testing image_proc nodelets, but seems like it needs the camera_info msg for every image_raw. but it shouldn't be necessary because most of the parameters are the same, and is just using cpu and memory.
Best regards Eduardo Soares
↧
↧