BloJJ

Adventures of a multidimensional freak

This is Juan Julián Merelo Guervós English-language blog. He teaches computer science at the University of Granada, in southern Spain. Come back here to read about politics, technology, with a new twist

Latest comments

  • Natasha en Riddles in Kafka on the shore
  • Cb en Riddles in Kafka on the shore
  • Dan Brown Freak en Spanish mostly pissed off at Dan Brown's Digital Fortress
  • Jack en Riddles in Kafka on the shore
  • Anónimo en About conference poster design and defense
  • Hendo en Riddles in Kafka on the shore
  • TML en Riddles in Kafka on the shore
  • Anonymous en Riddles in Kafka on the shore
  • RonS en Riddles in Kafka on the shore
  • miss en Riddles in Kafka on the shore
  • Blogs Out There

    Nelson Minar's Blog
    Jeremy Zawodny's Blog
    Kottke
    Complexes, Carlos Gershenson's blog
    IlliGAL, Genetic Algorithms blog
    Blogging in the wind, Víctor R. Ruiz's blog


    Atalaya, my Spanish language blog
    Geneura@Wordpress, our research group's blog.
    My home page

    Old stories


    Creative Commons License
    This work is licensed under a Creative Commons License.
    Blogalia

    Stats
    Inicio > Historias > How open should research be?

    How open should research be?

    Lately, we are moving all our software development to public forges such as Google Code or the Spanish RedIris forge. This implies that whatever we're working in, our next PhD, congress paper code is open for anybody to see, should anyone be interested in it. Besides thinking that this is a good thing, I don't really think anybody cares about what anybody else is working in to steal from the server and publish it withouth mentioning authorship. Besides, it makes things so much easier: just offload development repositores somewhere else, without having to worry about downtimes, security, or anything else.
    I wonder if we should take this a bit, just a bit, further, by putting also papers in development in the same repository. Again, who would care? And it would make life so much easier... never having to worry about what version is it you're working in... just check out, do stuff, check in again. But I don't know if that will make development a bit cumbersome, by leaving there for all to see all comments done on the LaTeX source code, and all blunders of the early versions. I think we'll give it a try, and see what happens...

    2008-01-11 18:20 | 8 Comment(s) | Filed in Just_A_Scientist

    Referencias (TrackBacks)

    URL de trackback de esta historia http://blojj.blogalia.com//trackbacks/54728

    Comentarios

    1
    De: Julian Togelius Fecha: 2008-01-11 19:22

    Good initiative. Maybe I should lobby for us doing the same for code at IDSIA... for paper-writing, however, I've been using Google Documents for a long time now - just dumping the LaTeX source in an online word processing document, and sharing it with collaborators. It works just as well as you would hope for, and has made various collaborations much easier. Once, four of us wrote a paper in one long night, all working simultaneously on the same document! I don't know if there's an option for making the document completely public though, but I think there is.



    2
    De: JJ Fecha: 2008-01-11 19:25

    That's a pretty good idea, actually... although I prefer my good old emacs with all the syntax highlight goodies to the Google Docs WYSIWYG interface.



    3
    De: Julian Togelius Fecha: 2008-01-11 21:16

    Yeah, I agree that it would be even better if GDocs highlighted the syntax as well, and possibly even did the compilation!



    4
    De: Juan Lupión Fecha: 2008-01-11 21:27

    I don't see Google Docs compiling LaTeX sources in the near future but that would be COOL.



    5
    De: Dave Oranchak Fecha: 2008-01-12 19:53

    This is not exactly on-topic but I was curious what you thought about Amazon's EC2 service as a platform for evolutionary computing:

    http://www.amazon.com/gp/browse.html?node=201590011

    The reason I am interested in it is because of the ability to scale the computing resources in several dimensions, and because I am outside of the university system and have no good access to high-powered computing hardware for my research. Do you know of anyone in the EC community taking advantage of Amazon's services? Is it even suitable for this?



    6
    De: JJ Fecha: 2008-01-13 11:08

    Hi, Dave. I also considered it. The concept is kinda interesting, but, unfortunately, it's for pay, so it's difficult to check it out on a whim. It would be ironic too, to use EC2 for EC (1).
    However, if the issue is scaling computing power for those who don't have it available, using AJAX or BOINC is an alternative; all you need is a host with access to a database. Did you check our paper on the subject?



    7
    De: Dave Oranchak Fecha: 2008-01-13 22:03

    Yes; I saw your paper, and I also attended your talk at GECCO - you presented several interesting options for distributed computing. Another talk I attended mentioned using the multiple processors on high-end video cards for EC. So there are many options to pick from, it seems!



    8
    De: JJ Fecha: 2008-01-15 22:47

    I have been checking out ECS, and from the purely theoretical point of view, it's no big deal: virtual machines available on demand. Plus, I'm afraid doing any experiment with would end up being expensive, even with the low machine-hour cost. And it does not fit well with the university paying processes.



    Nombre
    Correo-e
    URL
    Dirección IP: 23.20.65.255 (3b2b457c65)
    Comentario

    © 2002 - 2008 jmerelo
    Powered by Blogalia