Group items tagged

Somehow, the mere fact does not surprise me. I always assumed that the genetic information is on multiple overlapping layers encoded. I do not see how this can be transferred exactly on genetic algorithms, but a good encoding on them is important and I guess that you could produce interesting effects by "overencoding" of parameters, apart from being more space-efficient.

Or: mathematicians catch up with open-source software developers :)

"Similar open-source techniques could be applied in fields such as [...] computer science, where the raw materials are informational and can be freely shared online." ... or we could reach the point, unthinkable only few years ago, of being able to exchange text messages in almost real time! OMG, think of the possibilities! Seriously, does the author even browse the internet?

I do not agree with you F., you are citing out of context! Sharing messages does not make a collaboration, nor does a forum, .... You need a set of rules and a common objective. This is clearly observable in "some team", where these rules are lacking, making team work inexistent. The additional difficulties here are that it involves people that are almost strangers to each other, and the immateriality of the project. The support they are using (web, wiki) is only secondary. What they achieved is remarkable, disregarding the subject!

I think we will just have to agree to disagree then :) Open source developers have been organizing themselves with emails since the early '90s, and most projects (e.g., the Linux kernel) still do not use anything else today. The Linux kernel mailing list gets around 400 messages per day, and they are managing just fine to scale as the number of contributors increases. I agree that what they achieved is remarkable, but it is more for "what" they achieved than "how". What they did does not remotely qualify as "massively" collaborative: again, many open source projects are managed collaboratively by thousands of people, and many of them are in the multi-million lines of code range. My personal opinion of why in the scientific world these open models are having so many difficulties is that the scientific community today is (globally, of course there are many exceptions) a closed, mostly conservative circle of people who are scared of changes. There is also the fact that the barrier of entry in a scientific community is very high, but I think that this should merely scale down the number of people involved and not change the community "qualitatively". I do not think that many research activities are so much more difficult than, e.g., writing an O(1) scheduler for an Operating System or writing a new balancing tree algorithm for efficiently storing files on a filesystem. Then there is the whole issue of scientific publishing, which, in its current form, is nothing more than a racket. No wonder traditional journals are scared to death by these open-science movements.

here we go ... nice controversy! but maybe too many things mixed up together - open science journals vs traditional journals, conservatism of science community wrt programmers (to me one of the reasons for this might be the average age of both groups, which is probably more than 10 years apart ...) and then using emailing wrt other collaboration tools .... .... will have to look at the paper now more carefully ... (I am surprised to see no comment from José or Marek here :-)

My point about your initial comment is that it is simplistic to infer that emails imply collaborative work. You actually use the word "organize", what does it mean indeed. In the case of Linux, what makes the project work is the rules they set and the management style (hierachy, meritocracy, review). Mailing is just a coordination mean. In collaborations and team work, it is about rules, not only about the technology you use to potentially collaborate. Otherwise, all projects would be successful, and we would noy learn management at school! They did not write they managed the colloboration exclusively because of wikipedia and emails (or other 2.0 technology)! You are missing the part that makes it successful and remarkable as a project. On his blog the guy put a list of 12 rules for this project. None are related to emails, wikipedia, forums ... because that would be lame and your comment would make sense. Following your argumentation, the tools would be sufficient for collaboration. In the ACT, we have plenty of tools, but no team work. QED

the question on the ACT team work is one that is coming back continuously and it always so far has boiled down to the question of how much there need and should be a team project to which everybody inthe team contributes in his / her way or how much we should leave smaller, flexible teams within the team form and progress, more following a bottom-up initiative than imposing one from top-down. At this very moment, there are at least 4 to 5 teams with their own tools and mechanisms which are active and operating within the team. - but hey, if there is a real will for one larger project of the team to which all or most members want to contribute, lets go for it .... but in my view, it should be on a convince rather than oblige basis ...

It is, though, indicative that some of the team member do not see all the collaboration and team work happening around them. We always leave the small and agile sub-teams to form and organize themselves spontaneously, but clearly this method leaves out some people (be it for their own personal attitude or be it for pure chance) For those cases which we could think to provide the possibility to participate in an alternative, more structured, team work where we actually manage the hierachy, meritocracy and perform the project review (to use Joris words).

I am, and was, involved in "collaboration" but I can say from experience that we are mostly a sum of individuals. In the end, it is always one or two individuals doing the job, and other waiting. Sometimes even, some people don't do what they are supposed to do, so nothing happens ... this could not be defined as team work. Don't get me wrong, this is the dynamic of the team and I am OK with it ... in the end it is less work for me :) team = 3 members or more. I am personally not looking for a 15 member team work, and it is not what I meant. Anyway, this is not exactly the subject of the paper.

My opinion about this is that a research team, like the ACT, is a group of _people_ and not only brains. What I mean is that people have feelings, hate, anger, envy, sympathy, love, etc about the others. Unfortunately(?), this could lead to situations, where, in theory, a group of brains could work together, but not the same group of people. As far as I am concerned, this happened many times during my ACT period. And this is happening now with me in Delft, where I have the chance to be in an even more international group than the ACT. I do efficient collaborations with those people who are "close" to me not only in scientific interest, but also in some private sense. And I have people around me who have interesting topics and they might need my help and knowledge, but somehow, it just does not work. Simply lack of sympathy. You know what I mean, don't you? About the article: there is nothing new, indeed. However, why it worked: only brains and not the people worked together on a very specific problem. Plus maybe they were motivated by the idea of e-collaboration. No revolution.

Joris, maybe I made myself not clear enough, but my point was only tangentially related to the tools. Indeed, it is the original article mention of "development of new online tools" which prompted my reply about emails. Let me try to say it more clearly: my point is that what they accomplished is nothing new methodologically (i.e., online collaboration of a loosely knit group of people), it is something that has been done countless times before. Do you think that now that it is mathematicians who are doing it makes it somehow special or different? Personally, I don't. You should come over to some mailing lists of mathematical open-source software (e.g., SAGE, Pari, ...), there's plenty of online collaborative research going on there :) I also disagree that, as you say, "in the case of Linux, what makes the project work is the rules they set and the management style (hierachy, meritocracy, review)". First of all I think the main engine of any collaboration like this is the objective, i.e., wanting to get something done. Rules emerge from self-organization later on, and they may be completely different from project to project, ranging from almost anarchy to BDFL (benevolent dictator for life) style. Given this kind of variety that can be observed in open-source projects today, I am very skeptical that any kind of management rule can be said to be universal (and I am pretty sure that the overwhelming majority of project organizers never went to any "management school"). Then there is the social aspect that Tamas mentions above. From my personal experience, communities that put technical merit above everything else tend to remain very small and generally become irrelevant. The ability to work and collaborate with others is the main asset the a participant of a community can bring. I've seen many times on the Linux kernel mailing list contributions deemed "technically superior" being disregarded and not considered for inclusion in the kernel because it was clear that

hey, just catched up the discussion. For me what is very new is mainly the framework where this collaborative (open) work is applied. I haven't seen this kind of working openly in any other field of academic research (except for the Boinc type project which are very different, because relying on non specialists for the work to be done). This raise several problems, and mainly the one of the credit, which has not really been solved as I read in the wiki (is an article is written, who writes it, what are the names on the paper). They chose to refer to the project, and not to the individual researchers, as a temporary solution... It is not so surprising for me that this type of work has been first done in the domain of mathematics. Perhaps I have an ideal view of this community but it seems that the result obtained is more important than who obtained it... In many areas of research this is not the case, and one reason is how the research is financed. To obtain money you need to have (scientific) credit, and to have credit you need to have papers with your name on it... so this model of research does not fit in my opinion with the way research is governed. Anyway we had a discussion on the Ariadnet on how to use it, and one idea was to do this kind of collaborative research; idea that was quickly abandoned...

I don't really see much the problem with giving credit. It is not the first time a group of researchers collectively take credit for a result under a group umbrella, e.g., see Nicolas Bourbaki: http://en.wikipedia.org/wiki/Bourbaki Again, if the research process is completely transparent and publicly accessible there's no way to fake contributions or to give undue credit, and one could cite without problems a group paper in his/her CV, research grant application, etc.

Well my point was more that it could be a problem with how the actual system works. Let say you want a grant or a position, then the jury will count the number of papers with you as a first author, and the other papers (at least in France)... and look at the impact factor of these journals. Then you would have to set up a rule for classifying the authors (endless and pointless discussions), and give an impact factor to the group...?

Riemann hypothesis should be next... Which paper on the linked website is this exactly?

hmmm, last year at the AIAA conference in Toronto I presented a continuation approach to design a DRO (three-body problem). Nothing new here unfortunately. I know the work of Caillau, although interesting what is presented was solved 10 years ago by others. The interest of his work is not in the applications (CR3BP), but in the research of particular regularity conditions that unfortunately make the problem limited practically. Look also at the work of Mingotti, Russel, Topputo and other for the (C)RTBP. Smart-One inspired a bunch of researchers :)

Topputo and some of the others 'inspired' researchers you mention are actually here at the conference and they are all quite depressed :) Caillau really solves the problem: as a one single phase transfer, no tricks, no misconvergence, in general and using none of the usual cheats. What was produced so far by other were only local solutions valid for the particular case considered. In any case I will give him your paper, so that he knows he is working on already solved stuff :)

Answer to Marek: the paper you may look at is: Discrete and differential homotopy in circular restricted three-body control

Ah! with one single phase and a first order method then it is amazing (but it is still just the very particular CRTBP case). The trick is however the homotopy map he selected! Why this one? Any conjugate point? Did I misunderstood the title ? I solved in one phase with second order methods for the less restrictive problem RTBP or simply 3-body... but as a strict answer to your title the problem has been solved before. Nota: In "Russell, R. P., "Primer Vector Theory Applied to Global Low-Thrust Trade Studies," JGCD, Vol. 30, No. 2", he does solve the RTBP with a first order method in one phase.

I think what is interesting is not what he solved, but how he solved the problem. But, are means more important than end ... I dunno

I also loved his method, and it looked to me that is far more general than the CRTBP. As for the title of this post, OK maybe it is an exageration as it suggests that no solution was ever given before, on the other end, as Marek would say "come on guys!!!!!"

The generality has to be checked. Don't you think his choice of mapping is too specific? he doesn't really demonstrate it works better than other. In addition, the minimum time choice make the problem very regular (i guess you've experienced that solving min time is much easier than mass max, optimality-wise). There is still a long way before maximum mass+RTBP, Topputo et al should be re-assured :p Did you give him my paper, he may find it interesting since I mention the homotopy on mu but for max mass:)

Joris, that is the point I was excited abut, at the conference HE DID present solutions to the maximum mass problem!! One phase, from LEO to an orbit around the moon .. amazing :) You will find his presentation on line.... (according to the organizers) I gave him the reference to you paper anyway, but no pdf though as you did not upload it on our web pages and I could not find it in the web. So I gave him some bibliography I had with be from the russians, and from Russell, Petropoulos and Howell, As far as I know these are the only ones that can hope to compete with this guy!!

for info only, my phd, in one phase: http://pdf.aiaa.org/preview/CDReadyMAST08_1856/PV2008_7363.pdf I prefered Mars than the dead rock Moon though!

If you send me the pdf I can give it to the guy .. the link you gave contains only the first page ... (I have no access till monday to the AIAA thingy)

this is why I like this Diigo thingy so much more than delicious ...

What do you mean by this comment, Leopold? ;-) Jokes apart: I am following the Diigo thingy with Google Reader (rss). Obviously, I am getting the new postings. But if someone later on adds a comment to a post, then I can miss it, because the rss doesn't get updated. Not that it's a big problem, but do you guys have a better solution for this? How are you following these comments? (I know that if you have commented an entry, then you get the later updates in email.) (For example, in google reader I can see only the first 5 comments in this entry.)

indeed ... already hotly debated in CDF ... any suggestions in addition to what we already contributed to this (e.g. system level optimisation)

well sure competitiveness is good but to verify (and that should be the case for scientific experiments) the code should be public, it would be nice to have something like bibtex for code libraries or versions used.... :) btw I fully agree that the code should go public, I had lots of trouble reproducing (reprogramming) some papers in the past ... grr