I officially propose removing DSage from the Sage distribution.
Why?
1. Nobody has worked on the code for years.
2. The guy who originally worked on the code is gone, and can't
work on the code even if he wanted to (due to conditions of his job).
3. So far as I can tell, DSage is completely and totally broken,
and has been for *months* in shipped versions of Sage, so absolutely
nobody could possibly be using it. See
http://trac.sagemath.org/sage_trac/ticket/7975
If you care, please vote.
[ ] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
[ ] No, I think DSage should stay as is. I love using DSage!
[ ] Sort of -- delete Dsage for now, but if a maintainer/developer
comes along and fixes it so it actually works, then DSage gets back
into Sage for free.
I vote for orphaning.
>
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
>
I vote:
[x] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
However, I admit that I have no idea of what it does. ;-)
Adam
I don't know if I care, but if I did, my answer would be
[X] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
And what is it?
Cheers
Simon
Nathann
John
2010/1/18 Nathann Cohen <nathan...@gmail.com>:
> Same question.. What is it ? ;-)
>
> Nathann
>
Rationale:
- For simplistic parallell computing on a single machine there's now
other, much simpler solutions implemented
- For running on a real cluster, I believe the approach is wrong. Most
clusters used in academia is run by a professional support staff and
have a sophisticated setup for scheduling jobs. I'd never get DSage set
up correctly on my cluster without pestering a lot of admins. However I
*can* of course integrate Sage with the cluster-provided job scheduling
system in user space if I want to. That's the way to go IMO.
- Running on a small home-brew cluster should a) fall outside of Sage's
scope, and b) use existing libraries rather than home-cooked to a much
larger extent than DSage does (use OpenMPI or Google's Map/Reduce or
something in-between).
Dag Sverre
On the basis of
* It does not work
* The maintainer can't even maintain it if he wished now (people do change jobs).
there does not seem a lot of point keeping it in standard, though I'd personally
probably prefer to move it to the experimental packages and add a note there
that it used to work, but no longer does.
might be a suitable replacement.
Distributed computing for some problems can be very useful.
So I would not remove it completely, but take it out of 'standard' and move to
'experimental'.
Dave
[x] Yes, I've used DSage extensively in the past, and I wholeheartedly
agree with removing it from Sage.
The only use I have for dsage anymore is "Hey! The dsage spkg is
compiling! Sage must be almost finished building!"
--
Robert L. Miller
http://www.rlmiller.org/
[X] Yes, I don't use DSage (don't even know what it is...), and
think it should be removed from Sage.
Well, I do know vaguely what it is, but I don't think it should get back
into standard without the usual review process---definitely not for free.
Moving it to experimental sounds like the best option to me.
Thanks,
Jason
I worked during months with my computer lab director trying to make
dsage work... We managed once to make it work properly.
In dsage:
-Documentation is anemic;
-Many not implemented functions;
-Bizarre behaviours
-...
My vote is:
[x] - Remove dSage from Sage "and use something else instead".
We resign from using dsage and we now use xgrid on Mac. I found that
Parallel Python could do the job too... I don't know much about this
library, but could it be added to sage some day? I would be glad to
help if we can add it to sage.
Jean-Philippe Labbé
> Hello,
>
> I officially propose removing DSage from the Sage distribution.
>
> Why?
>
> 1. Nobody has worked on the code for years.
>
> 2. The guy who originally worked on the code is gone, and can't
> work on the code even if he wanted to (due to conditions of his job).
>
> 3. So far as I can tell, DSage is completely and totally broken,
> and has been for *months* in shipped versions of Sage, so absolutely
> nobody could possibly be using it. See
> http://trac.sagemath.org/sage_trac/ticket/7975
>
> If you care, please vote.
>
> [X] Yes, I don't use DSage (though I certainly know what it
> is...), and
> think it should be removed from Sage.
If it's been broken for a while, there aren't backwards compatibility
issues to worry about. I second moving this package out to experimental.
- Robert
Nathan
--
To post to this group, send an email to sage-...@googlegroups.com
To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
I'm in this group, but I do know one (possibly the only?) DSage user
-- John Voight. Does anyone know if he still uses it?
-cc
DSage is now gone from Sage. See
http://trac.sagemath.org/sage_trac/ticket/7975
-- William
> --
> To post to this group, send an email to sage-...@googlegroups.com
> To unsubscribe from this group, send an email to sage-devel+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
Dag Sverre Seljebotn wrote:
> - For running on a real cluster, I believe the approach is wrong. Most
> clusters used in academia is run by a professional support staff and
> have a sophisticated setup for scheduling jobs. I'd never get DSage set
> up correctly on my cluster without pestering a lot of admins. However I
> *can* of course integrate Sage with the cluster-provided job scheduling
> system in user space if I want to. That's the way to go IMO.
Do you mean you can write an interface for, let's say, TorquePBS/Maui
submition ?
That would be very much useful.
I'll send you an invitation to sage-grid mailing list. May be we could
elaborate smth interesting for cluster environment.
>
> Dag Sverre
>
#Serge