ORBIT-USER: Node image repository?

[Ivan Seskar]

Hi Einar,

That is on our to-do list (for about a year now and somewhere around
item #38 :-) ); as a matter of fact the whole user portal needs a lot of
work. In the meantime (and this of course applies to every Orbit user),
if you are willing to share your images please just go ahead and add an
entry to the table at
http://www.orbit-lab.org/wiki/Documentation/UserContributedImages (that
page is linked off the "main" image page at
http://www.orbit-lab.org/wiki/Documentation/SupportedImages ; we may
need to reorganize our wiki content to make it easier to find these
pages ).

Regards,

Ivan.

-----Original Message-----
From: owner-orbit-user at winlab.rutgers.edu
[mailto:owner-orbit-user at winlab.rutgers.edu] On Behalf Of Einar Vollset
Sent: Monday, August 28, 2006 6:11 PM
To: orbit-user at winlab.rutgers.edu
Subject: ORBIT-USER: Node image repository?



Hi,

I was wondering - how much work would it be to create a node image
repository with a web interface? I'm thinking of something like the
ability to describe and make publicly available a saved node image (note
that by "making available" I don't downloadable from the website, but
accessible from the orbit-lab consoles).

This would be quite useful, not only to people like me lacking the
mental capacity to remember what the node images are called, or indeed
which one does what, but also as it may cut down on replication of work,
encourage cooperation and heighten the profile of good, real wireless
systems built.

For example, if researcher A works on MAC scheduling algorithms, and
(doing some good work) gets it published in MobiCom, he could put up a
page describing the node image, and then reference that in his paper.

Researcher B, being more interested in routing protocols, could then use
researcher A's image to build his system over. When researcher B then
comes to write his paper, he references researcher A's image & paper.

Going even further you could imagine researcher C (a surly type)
deciding that researcher A's MAC protocol is crap, and building his own
to beat it. He then does a performance test between his new algorithm
and researcher A's (as he easily has that available), publishes a paper,
etc, etc..

You could even give a prize to the most used node image, or most
reference node image. ;-)

Cheers,

Einar






------------------------------------------------------
Einar Vollset
Visiting Assistant Professor
Department of Computer Science
Cornell University

Phone: +1-607-255-7573
Web: http://www.cs.cornell.edu/~einar
------------------------------------------------------