1 Aug 04:22
Re: Bio::Moose is now....
Chris Fields <cjfields <at> illinois.edu>
2009-08-01 02:22:17 GMT
2009-08-01 02:22:17 GMT
I think, before any CPAN release, I want to nip the monolith in the bud. Just have Meta/Root and simple interfaces (roles) describing classes in Biome, actual implementations or other additions going into BiomeX::*. The current Biome::Location/Annotation/etc would eventually be moved into their own BiomeX repos. Bundle with Task::Biome (maybe add some automated bundling options). Sound familiar? I'll try to get a ROADMAP up next week. chris On Jul 31, 2009, at 9:53 AM, Robert Buels wrote: > I think this sounds great. GREAT news about the Biome::PrimarySeq > performance. > > Rob > > Chris Fields wrote: >> Biome! This makes the most sense to me; as Mark points out the >> name works as an appropriate acronym (BioPerl with Metaclass >> Extensions), as well as a biome being (per wikipedia): >> "a climatically and geographically defined areas of ecologically >> similar climatic conditions such as communities of plants, animals, >> and soil organisms ... often referred to as ecosystems". >> Seems a fitting name for a open-source project. I'll be moving the >> namespace over to Biome over the next couple of days on github. >> Now I owe Mark some beer... >> Now, for extensions, should I assume this will eventually be(Continue reading)
>
> Now I just need a bit of free time to get it working...
>
> --Russell
>
>
>
I agree, that's probably the best way to go. It's hard to know what
amount of s/w processing was done on the host PC vs. the embedded
controller. If you were able to connect directly to the robot hardware
with serial port(s) or whatever it's using, it would be tough to find
out the comm protocol unless someone has already reverse engineered it
(which is doubtful). Also from what I have seen online, attempting to
run the old software under virtual machine is unpredictable due to
timing differences in the serial port communication. So removal of the
old electronics is probably the best bet. If it has one arm, then it's
much easier.
As for robots with working workstation software, it seems the annoyance
factor is that while the scripting languages are powerful (for GUI
scripting that is), they are still relatively low level. Bio types with
a bit of CS seem to immediately turn to visual basic, labview, or even
excel spreadsheets and macros, in order to provide a higher level
abstraction for the workstation software. To me, it seems natural that
RSS Feed