Where to find the rtt2-converter script??

Submitted by Ruben Smits on Wed, 2010-06-23 07:28

RTT-dev

Hi Devs,

I have been looking for the rtt2-converter script on the website for 15
minutes and still haven't found it yet.

Conclusion: It is way to hard to find, we should at least provide a link on the
Upgrading from RTT 1.x to 2.0 page
<http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>

Ruben

Where to find the rtt2-converter script??

Submitted by peter on Wed, 2010-06-23 07:32.

On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> Hi Devs,
>
> I have been looking for the rtt2-converter script on the website for 15
> minutes and still haven't found it yet.
>
> Conclusion: It is way to hard to find, we should at least provide a link on
> the Upgrading from RTT 1.x to 2.0 page
> <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>

You can find it at the end of the rtt 2.0 renaming table:

http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table

We should put the text on that page on top and indeed link to it from the
upgrading page. The script is slightly outdated, especially regarding the
toolkits renaming, which is not yet on 2.0-mainline.

Peter

Where to find the rtt2-converter script??

Submitted by Ruben Smits on Wed, 2010-06-23 07:36.

On Wednesday 23 June 2010 09:29:42 Peter Soetens wrote:
> On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> > Hi Devs,
> >
> > I have been looking for the rtt2-converter script on the website for 15
> > minutes and still haven't found it yet.
> >
> > Conclusion: It is way to hard to find, we should at least provide a link
> > on
> >
> > the Upgrading from RTT 1.x to 2.0 page
> >
> > <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>
>
> You can find it at the end of the rtt 2.0 renaming table:
>
> http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
>
> We should put the text on that page on top and indeed link to it from the
> upgrading page. The script is slightly outdated, especially regarding the
> toolkits renaming, which is not yet on 2.0-mainline.

The tar seems to be corrupted?:

tar -xjf rtt2-converter-0.2.tar.bz2

bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files

Ruben

> Peter

Where to find the rtt2-converter script??

Submitted by peter on Wed, 2010-06-23 07:52.

On Wednesday 23 June 2010 09:32:57 Ruben Smits wrote:
> On Wednesday 23 June 2010 09:29:42 Peter Soetens wrote:
> > On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> > > Hi Devs,
> > >
> > > I have been looking for the rtt2-converter script on the website for 15
> > > minutes and still haven't found it yet.
> > >
> > > Conclusion: It is way to hard to find, we should at least provide a
> > > link on
> > >
> > > the Upgrading from RTT 1.x to 2.0 page
> > >
> > > <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>
> >
> > You can find it at the end of the rtt 2.0 renaming table:
> >
> > http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
> >
> > We should put the text on that page on top and indeed link to it from the
> > upgrading page. The script is slightly outdated, especially regarding the
> > toolkits renaming, which is not yet on 2.0-mainline.
>
> The tar seems to be corrupted?:
>
> tar -xjf rtt2-converter-0.2.tar.bz2
>
> bzip2: Compressed file ends unexpectedly;
> perhaps it is corrupted? *Possible* reason follows.
> bzip2: Inappropriate ioctl for device
> Input file = (stdin), output file = (stdout)
>
> It is possible that the compressed file(s) have become corrupted.
> You can use the -tvv option to test integrity of such files.
>
> You can use the `bzip2recover' program to attempt to recover
> data from undamaged sections of corrupted files

Same here. I'll upload a new version and let you know on the list.

Peter

Where to find the rtt2-converter script??

Submitted by Ruben Smits on Wed, 2010-06-23 07:44.

The functional code is apparently no in the tar :s.

Peter, can you provide a full version?

Ruben

> Ruben
>
> > Peter

Where to find the rtt2-converter script??

Submitted by peter on Wed, 2010-06-23 08:20.

On Wednesday 23 June 2010 09:41:59 Ruben Smits wrote:
> On Wednesday 23 June 2010 09:32:57 Ruben Smits wrote:
> > On Wednesday 23 June 2010 09:29:42 Peter Soetens wrote:
> > > On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> > > > Hi Devs,
> > > >
> > > > I have been looking for the rtt2-converter script on the website for
> > > > 15 minutes and still haven't found it yet.
> > > >
> > > > Conclusion: It is way to hard to find, we should at least provide a
> > > > link on
> > > >
> > > > the Upgrading from RTT 1.x to 2.0 page
> > > >
> > > > <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>
> > >
> > > You can find it at the end of the rtt 2.0 renaming table:
> > >
> > > http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
> > >
> > > We should put the text on that page on top and indeed link to it from
> > > the upgrading page. The script is slightly outdated, especially
> > > regarding the toolkits renaming, which is not yet on 2.0-mainline.
> >
> > The tar seems to be corrupted?:
> >
> > tar -xjf rtt2-converter-0.2.tar.bz2
> >
> > bzip2: Compressed file ends unexpectedly;
> > perhaps it is corrupted? *Possible* reason follows.
> > bzip2: Inappropriate ioctl for device
> > Input file = (stdin), output file = (stdout)
> >
> > It is possible that the compressed file(s) have become corrupted.
> > You can use the -tvv option to test integrity of such files.
> >
> > You can use the `bzip2recover' program to attempt to recover
> > data from undamaged sections of corrupted files
>
> The functional code is apparently no in the tar :s.
>
> Peter, can you provide a full version?

We have quota problems on orocos.org, which may have led to the truncation of
the file. I have uploaded the file to this place:

http://people.mech.kuleuven.be/~orocos/pub/devel/tools/rtt2-converter/

The tool takes some time to compile, please provide some feedback how it
(doesn't) works.

Peter

Where to find the rtt2-converter script??

Submitted by Ruben Smits on Wed, 2010-06-23 10:16.

On Wednesday 23 June 2010 10:15:48 Peter Soetens wrote:
> On Wednesday 23 June 2010 09:41:59 Ruben Smits wrote:
> > On Wednesday 23 June 2010 09:32:57 Ruben Smits wrote:
> > > On Wednesday 23 June 2010 09:29:42 Peter Soetens wrote:
> > > > On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> > > > > Hi Devs,
> > > > >
> > > > > I have been looking for the rtt2-converter script on the website
> > > > > for 15 minutes and still haven't found it yet.
> > > > >
> > > > > Conclusion: It is way to hard to find, we should at least provide a
> > > > > link on
> > > > >
> > > > > the Upgrading from RTT 1.x to 2.0 page
> > > > >
> > > > > <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>
> > > >
> > > > You can find it at the end of the rtt 2.0 renaming table:
> > > >
> > > > http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
> > > >
> > > > We should put the text on that page on top and indeed link to it from
> > > > the upgrading page. The script is slightly outdated, especially
> > > > regarding the toolkits renaming, which is not yet on 2.0-mainline.
> > >
> > > The tar seems to be corrupted?:
> > >
> > > tar -xjf rtt2-converter-0.2.tar.bz2
> > >
> > > bzip2: Compressed file ends unexpectedly;
> > >
> > > perhaps it is corrupted? *Possible* reason follows.
> > >
> > > bzip2: Inappropriate ioctl for device
> > >
> > > Input file = (stdin), output file = (stdout)
> > >
> > > It is possible that the compressed file(s) have become corrupted.
> > > You can use the -tvv option to test integrity of such files.
> > >
> > > You can use the `bzip2recover' program to attempt to recover
> > > data from undamaged sections of corrupted files
> >
> > The functional code is apparently no in the tar :s.
> >
> > Peter, can you provide a full version?
>
> We have quota problems on orocos.org, which may have led to the truncation
> of the file. I have uploaded the file to this place:
>
> http://people.mech.kuleuven.be/~orocos/pub/devel/tools/rtt2-converter/
>
> The tool takes some time to compile, please provide some feedback how it
> (doesn't) works.

* It does not change the headers or namespaces, but I suppose another tool does this.

* It does not remove the initial value in the constructor of an OutputPort:
original code :

inChannelPort( "InputValues", std::vector<double>( max_outchannels.get(), 0.0)

should have become:
inChannelPort( "InputValues")
+ somewhere (constructor?)
inChannelPort.setDataSample(std::vector<double>( max_outchannels.get(), 0.0))

* the addPort(port, documentation_string) does not get replaced by addPort(port).doc(documentation_string)

* some .provides are included at the wrong places:
diff:
- AnalogInInterface* input = AnalogInInterface::nameserver.getObject(devicename);
+ dev::AnalogInInterface* input = dev::AnalogInInterface::nameserver.provides(devicename);

this should have stayed as the original

* the old exportPorts() does not get removed

* the old removeObject() does not get removed but replaced by a non existing removeService:
- this->removeObject( Portname );
+ this->removeService( Portname );

And there were some Get/Set methods on Ports which did not get replaced.

Ruben

> Peter

Where to find the rtt2-converter script??

Submitted by peter on Wed, 2010-06-23 10:40.

On Wednesday 23 June 2010 12:14:18 Ruben Smits wrote:
> On Wednesday 23 June 2010 10:15:48 Peter Soetens wrote:
> > On Wednesday 23 June 2010 09:41:59 Ruben Smits wrote:
> > > On Wednesday 23 June 2010 09:32:57 Ruben Smits wrote:
> > > > On Wednesday 23 June 2010 09:29:42 Peter Soetens wrote:
> > > > > On Wednesday 23 June 2010 09:26:05 Ruben Smits wrote:
> > > > > > Hi Devs,
> > > > > >
> > > > > > I have been looking for the rtt2-converter script on the website
> > > > > > for 15 minutes and still haven't found it yet.
> > > > > >
> > > > > > Conclusion: It is way to hard to find, we should at least provide
> > > > > > a link on
> > > > > >
> > > > > > the Upgrading from RTT 1.x to 2.0 page
> > > > > >
> > > > > > <http://www.orocos.org/wiki/rtt/rtt-20/upgrading-rtt-1x-20>
> > > > >
> > > > > You can find it at the end of the rtt 2.0 renaming table:
> > > > >
> > > > > http://www.orocos.org/wiki/rtt/rtt-20/rtt-20-renaming-table
> > > > >
> > > > > We should put the text on that page on top and indeed link to it
> > > > > from the upgrading page. The script is slightly outdated,
> > > > > especially regarding the toolkits renaming, which is not yet on
> > > > > 2.0-mainline.
> > > >
> > > > The tar seems to be corrupted?:
> > > >
> > > > tar -xjf rtt2-converter-0.2.tar.bz2
> > > >
> > > > bzip2: Compressed file ends unexpectedly;
> > > >
> > > > perhaps it is corrupted? *Possible* reason follows.
> > > >
> > > > bzip2: Inappropriate ioctl for device
> > > >
> > > > Input file = (stdin), output file = (stdout)
> > > >
> > > > It is possible that the compressed file(s) have become corrupted.
> > > > You can use the -tvv option to test integrity of such files.
> > > >
> > > > You can use the `bzip2recover' program to attempt to recover
> > > > data from undamaged sections of corrupted files
> > >
> > > The functional code is apparently no in the tar :s.
> > >
> > > Peter, can you provide a full version?
> >
> > We have quota problems on orocos.org, which may have led to the
> > truncation of the file. I have uploaded the file to this place:
> >
> > http://people.mech.kuleuven.be/~orocos/pub/devel/tools/rtt2-converter/
> >
> > The tool takes some time to compile, please provide some feedback how it
> > (doesn't) works.
>
> * It does not change the headers or namespaces, but I suppose another tool
> does this.

Yes, you need to run *first* the to-rtt-2.0.pl script, then the rtt2-converter!
(although I think the order is not that important, but that's how I tested it
:-) )

>
> * It does not remove the initial value in the constructor of an OutputPort:
> original code :
>
> inChannelPort( "InputValues", std::vector<double>(
> max_outchannels.get(), 0.0)
>
> should have become:
> inChannelPort( "InputValues")
> + somewhere (constructor?)
> inChannelPort.setDataSample(std::vector<double>(
> max_outchannels.get(), 0.0))

Correct, setDataSample belongs in the constructor or in configureHook(). You
need to do this manually. I could try to glue it at the beginning of
configureHook() or even the constructor. Users can then copy/paste the line to
a better place if necessary...

>
> * the addPort(port, documentation_string) does not get replaced by
> addPort(port).doc(documentation_string)

Strange ! It should/must replace that (see rtt2-converter.cpp line 348).

>
> * some .provides are included at the wrong places:
> diff:
> - AnalogInInterface* input =
> AnalogInInterface::nameserver.getObject(devicename); +
> dev::AnalogInInterface* input =
> dev::AnalogInInterface::nameserver.provides(devicename);
>
> this should have stayed as the original

Ouch, name clash. I can't do much about this... except maybe requireing that
the "nameserver." is not preceeding getObject. I'll add this check at least.

>
> * the old exportPorts() does not get removed

Ok, added this.

>
> * the old removeObject() does not get removed but replaced by a non
> existing removeService: - this->removeObject( Portname );
> + this->removeService( Portname );

In which situation is removeObject() used ? How does removeService fail to
cope with that situation ?

>
>
> And there were some Get/Set methods on Ports which did not get replaced.

Hmm, rtt2-converter should do it, could you send the file that you used
(integral) ?

Thanks for the feedback,

Peter

Where to find the rtt2-converter script??

Submitted by Ruben Smits on Wed, 2010-06-23 08:24.

apparently there are two typos in the makefile;

make
Build with CPPFLAGS=-DSHORT_NOTATION to convert to the short notation of
adding or getting primitives:
Short notation: peer->getProperty(foo) Long notation: peer->properties()-
>getProperty(foo).
Short notation: this->addProperty( foo ) Long notation: this->properties()-
>addProperty( foo ).
/bin/sh: Syntax error: Unterminated quoted string
make: *** [all] Error 2

You missed a quote in the second to last echo and it should be CPP_FLAGS
instead of CPP_FLAG

Ruben

> Peter