Resonance.

I might suggest:
1) a set of default parameters that work fine for your casual, first-time
user (or a few sets, corresponding to "LAN," "Wifi," etc.)
2) a calibration tool that can measure network utilization and capacity of
you particular nodes on your particular network and then tweak the settings
for you (preferably both live and in an a priori calibration stage)
3) API hooks to give nodes a simple way to be notified that the pipes are
clogged and adjust accordingly.
4) a debug tool, a.k.a., rosnetwtf

Doing it right will take some work, but I think it'll be worth it to enough
people, and the advanced features can be spooled out incrementally over
time.

Thanks,
-Nick

-----Original Message-----
From: ros-users-bounces@lists.ros.org
[mailto:ros-users-bounces@lists.ros.org] On Behalf Of Ryan Gariepy
Sent: Friday, February 14, 2014 9:05 AM
To: User discussions
Subject: Re: [ros-users] ROS & DDS

Ease of use is *critical*. We're already receiving regular feedback that the
usability of ROS is getting worse with each distribution.

-Ryan

On Fri, Feb 14, 2014 at 8:43 AM, Ingo Lütkebohle <iluetkeb@gmail.com> wrote:
> On Fri, Feb 14, 2014 at 2:27 PM, Edwards, Shaun M. <sedwards@swri.org>
wrote:
>> My main concerns is Geoffrey Biggs' comment below.  Tuning should be 
>> a dirty word in software.  I know it's needed, but successful software
just works.
>> Ease of use should always be our focus.  It is this single issue that 
>> has been the nail in the coffin of every middleware I have used.
>
> I agree on that.
>
> One could reasonably argue that the attempt to solve the communication 
> problem in a relatively application-independent manner is doomed, and 
> that application-specific protocols are the way to go. Some people may 
> dismiss that as unrealistic, but I would argue that 
> application-specific protocols are the IETF approach, and that it has 
> been fairly successful, so far.
>
> That said, there is a question of what the basis for such developments 
> should be, or, in other words, whether the protocols in the DDS family 
> are a better foundation for robotics applications than base-level 
> TCP/IP.
>
> I guess answers to that question will be influenced significantly by 
> whether you're coming from an enterprise environment, or from an open 
> systems environment.
>
> cheers
>
> --
> Ingo Lütkebohle, Dr.-Ing.
> Machine Learning and Robotics Lab, IPVS, Universität Stuttgart 
> http://www.ipvs.uni-stuttgart.de/abteilungen/mlr/abteilung/mitarbeiter
> /Ingo.Luetkebohle
> +49-711-685-88350
>
> PGP Fingerprint 3187 4DEC 47E6 1B1E 6F4F  57D4 CD90 C164 34AD CE5B 
> _______________________________________________
> ros-users mailing list
> ros-users@lists.ros.org
> http://lists.ros.org/mailman/listinfo/ros-users
_______________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users