Dear Sage devs,
The fall school on Discrete Mathematics in Bobo Dioulasso, Burkina
Faso, aka Sage Days 43, just finished. For two weeks we had courses
(combinatorics of words, dynamics, tilings, ...) interspersed with
on-hands tutorials using Sage. The public consisted mostly from
graduate students, from subsaharian Africa and some further away
countries.
That was a good occasion for a real-life evaluation of a claim I have
been desiring to make for a long time: �Sage, being open-source, is
well adapted for universities in developing countries�.
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> I also hit the problem that Macs don't boot from USB, which IMHO is
> completely retarded, but that's just life.
That's a question for Jan Groenewald :-)
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Do you know much of it? Does it allow
1) to surpass a 4G limit?
2) to do a standard install from the ISO, including creating users, it simply adds extra packages transparent to the user?
3) allow adding of new sources.list.d files to the install target easily?
Regards,
Jan
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
The 4G limit: http://www.remastersys.com/ubuntu.html see the section
titled "The 4GB limit explained - not a remastersys limitation".
On Sun, Nov 11, 2012 at 08:07:06PM -0800, Mike Zabrocki wrote:
> Wow! Nicolas fantastic report. That was a challenge to do.
Thanks :-)
> I hope you managed a convert or two in Africa. My experience with
> computer classes as part of a summer school (in Ghana, Kenya,
> Tanzania and Madagascar) is similar except I never had a wifi
> network and most of my students didn't have regular computer access.
> Most of my students were complete novices to the computer, but
> willing to learn. Installing sage was several steps beyond what we
> tried. I would say that most of the infrastructure that we had
> access to would not support sage (most computers were dated
> pre-python, though I did not have the expertise to make this work).
I could hope for 4-5 that will use Sage in the long run, and 20 that
definitely see the point but will get stuck by lack of infrastructure
and expertise.
But as you said: �if our problem was only network, we were in pretty
good shape to start with�. We had a selection of students that were
definitely computer-literate (somehow, the main difficulty was to
prevent them from running to facebook&all and eat up all the bandwidth
whenever the network was working :-) ), even though most did not have
programming experience.
> I think to break the barrier and make a true sage days really
> productive, I think that you would need to partner with some
> organization like OLPC (one laptop per child) or arrange to
> minimize the problems with your hardware.
Well, I have a good contact for that: dad :-) We actually already used
Sage on our home OLPC, although only through a remote Sage server. I
doubt the old models can support running Sage locally, but for the
upcoming models we certainly will have a shot (at least running in a
terminal).
Of course, the real thing would be to integrate a resource-optimized
version of Sage within the Sugar activities. This probably won't be a
priority for OLPC, since their main target population is children of
age 6-12, but as you say we could explore other organizations as well.
Cheers,
Nicolas
--
Nicolas M. Thi�ry "Isil" <nth...@users.sf.net>
http://Nicolas.Thiery.name/
Hi,
thanks Nicolas for this exhaustive report. I would like to witness this
adventure it in a more pessimistic way, so that people willing to host
such a sage days know what kind of problems will appear, and which
workarounds are realistic.
I know very little about all the technicalities of these reports but want to echo that it is VERY valuable to have these real-life experiences - what a great thread.I recommend that several of these analyses be put on a wiki page linked to http://wiki.sagemath.org/#Hosting_a_workshop - maybe "How to host a Sage Days with older hardware and limited bandwidth", since that could even obtain in certain developed world locales outside of universities, and then people wouldn't have to search sage-devel for this information.
- Having more Sage mirrors in Africa (although the network issues were
more in the last kilometer).
That was a good occasion for a real-life evaluation of a claim I have
been desiring to make for a long time: �Sage, being open-source, is
well adapted for universities in developing countries�.
But perhaps I'm wrong and you also spread the word that some good open-source math softwares run on say Windows XP (or even Windows 98).
I'm curious: how does the software selection compare to, for example, mathbuntu (http://www.mathbuntu.org/), particularly the math packages?
But then why should developing countries use an old, buggy and proprietary software when they can get for free modern, top class open source operating systems? :)
Dear Sage devs,
The fall school on Discrete Mathematics in Bobo Dioulasso, Burkina
Faso, aka Sage Days 43, just finished. For two weeks we had courses
(combinatorics of words, dynamics, tilings, ...) interspersed with
on-hands tutorials using Sage. The public consisted mostly from
graduate students, from subsaharian Africa and some further away
countries.
That was a good occasion for a real-life evaluation of a claim I have
been desiring to make for a long time: �Sage, being open-source, is
well adapted for universities in developing countries�.
Let's see about this.
A couple words of context:
--------------------------
- 70 participants total; in average 40-50 were there.
- Most participants had a laptop (or netbook for a few of them):
- 90%: windows, 5% mac, 5% Linux Ubuntu (usually in double-boot with Windows)
- Laptop age ranging from 2003 to 2012; 4 years on average
- RAM: 500k-6Gb; 1Gb on average?
- Network: one ADSL line for 60 persons in the conference center
Well, when it actually worked, which was not that often.
We finished using a cell-phone shared over wifi.
The local wireless network itself was down quite often.
No network at the university itself or nearby
- Among the organizers were Sage devs with good experience on running
Sage workshops and doing system/network administration, ...
- Sam had brought a big bunch of power cables. I screwed up not
bringing my own wireless router to at least guarantee a reliable
local network.
Strategies we tried or considered:
----------------------------------
(a) Installing Sage on Linux/Mac with the binaries from Sagemath.org
(b) Installing Sage on Linux/Mac from sources
(c) Installing Sage on Linux from a custom built fat binary
(d) Installing Sage on Windows with the virtual machine
(e) Running a Sage server on my laptop (8 cores, 8Gb)
(f) Using a remote Sage server
(g) Installing Linux and reducing the problem to (a-c)
(h) Booting on a live Debian USB key, custom-build by Thierry Monteil
with Sage, self-cloning and persistence.
(i) Using a local PC lab after installing Sage on them
I would like to use the occasion to send my kudos to all those who
strive hard at making Sage easier to use one way or the other.
How it went:
------------
(a) Went smoothly on Mac when appropriate binaries were available. We
had to recompile a few of those binaries.
(a) failed most of the time on Linux by lack of gfortran. Since we did
not have a reasonable network, apt-get install was not an option.
We did not have iso's of all the Ubuntu versions that were in use.
3D plotting was usually not available (by lack of appropriate Java
plug-ins).
(b) Compiling from source was not a viable option on Linux for the
same reason as above: build-essentials was usually not there. On
Mac that was ok, provided we had under hand the appropriate
version of XCode.
(c) This fat binary was built by Thierry Monteil on an old pentium 3
(!) with a minimal Debian install. Installation and usage went
smoothly, except that 3D plotting was usually not available.
(d) Virtual machine: Installation went smoothly on about 20 machines
(with close guidance). It failed on 2-3 machines due to resource
limitations (disk, ...).
However, except for about five recent machines, the memory
footprint was just too high: any non trivial calculation or plot
made the laptop swap and become simply too slow to use.
The french keyboard was not properly self-detected. Due to the
network, we could not look up on the web for help. We ended up
finding how to configure it from a shell. I'll create a ticket.
The Sage version available was a bit old (5.1) though that was not
an issue for us this time (but it could have been).
The usage was on the complex side for most participants. They
typically tended to reclick on the ova, creating a new virtual
machine each time. Also uploading worksheets was tricky; it would
be much simpler if the virtual machine was setup to access the
user directory on the host machine or if the web client was
running on the host.
(e) Running a local Sage server: This is a priori good short term
solution, except that participants don't leave with Sage running
on their machine. My laptop easily handled the dozen people using
it. However the unreliability of the local wireless network ruined
the game more often than not. We have no data for how this would
have scaled if all participants had gone this way.
(f) Using a remote Sage server: given the network situation, we did
not even bother trying.
(g) Installing Linux, 3-4 machines: we were of course all favorable
to encourage participants to switch to Linux. However, installing
a new system always means taking a risk, especially since most
participants did not have backups (or even did not have a clue
what a backup was ...). Besides we did not want to spend too much
time on system administration.
(h) Live USB key, ~30 machines: this worked smoothly on most PC's
after fighting a bit with the BIOS to boot from USB. Some HP
laptops resisted. Pro: we could include some extra documents
(tutorial files, ...) on the key. Con: it forced people out of
their usual work environment. The self-cloning was an important
feature to quickly replicate updated versions of the key (log(n)),
and promote future diffusion around the participants.
(i) Local PC lab: we ended up dropping the idea because the available
PC labs either lacked network or electrical power. Potential pros
and cons: more consistent hardware simplifies the
installation. But the hardware tends to be older. The room can
possibly be used for running Sage in the long run. But the
participant don't leave with Sage running on their machine.
Summary:
--------
- The two main bottlenecks were network and available memory.
- The virtual machine seldom was a viable option.
- The Live USB key was by far the most robust option, though not ideal
for long term use by the participants (and it does not work on Mac,
or at least not easily).
- We really had to plan for multiple strategies to ensure that at
least one would work for each participant.
- It seems unlikely that someone without serious Sage experience would
have a chance to setup a Sage tutorial in similar (and alas typical)
conditions.
Altogether, and for what it's worth, this experience suggests that
Sage sill has quite some way to go before we can claim that it is
indeed well adapted for universities in developing countries.
Recommendations:
----------------
Of course one could rightfully argue that things would be *much*
easier if Linux was more widely spread in universities with little
resources (which would make a lot of sense as well). But since we
can't do much on that front at the Sage scale, here are some tentative
recommendations for improving Sage itself:
- Sage on Windows: there *is* an important use case for having a
native port of Sage on Windows. Over time, the virtual machine *may*
become a viable option as memory limitations become less
stringent. For this, it is crucial to reduce the memory footprint to
its bare minimum. Using the host web browser is the most obvious
step.
- Precompiled binary for Linux: besides the usual distro-specific
binaries, it would be very helpful to have two (32bit / 64bit) fat
Sage binaries that would work without dependencies on as many
distros and processors as possible. Even if this means a slightly
larger archive and lack of optimizations on recent
processors. Compiling on a Pentium 3 was probably overkill, but
Pentium 4 would be good at this point in time. If there is a way to
include Java plugins that would be great as well.
I let Thierry Monteil comment more on how he built those binaries.
- Having more Sage mirrors in Africa (although the network issues were
more in the last kilometer).
- Keeping on reducing the Sage's startup time and memory by lazy
importing more stuff in Sage.
Again, kudos to all who strive and will strive at improving the
usability of Sage!
Cheers,
Nicolas
--
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Nicolas M. Thiéry "Isil" <nth...@users.sf.net>
http://Nicolas.Thiery.name/
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
I have now used UCK to make a "Live CD" which has sagemath-upstream-binary from the PPA.
It is also Ubuntu 12.04.1 with a dist-upgrade up to the latest versions, and a few other packages
I like (it is debatable what can be included here). It is a 1.6G ISO which can be written to a USB stick.
It is fairly trivial to add languages, developer tools, rstudio, texmaker, etc.
I'd suggest a large system for generic use, to not duplicate effort: texmaker, scipy, many python
libraries, R, rstudio, sysadm tools, dev tools, sage, some graphics apps, and general utilities, including
English, French, Arabic, Amharic, Spanish, Portuguese, Mandarin, Italian, Polish, German, Romanian,
Finnish, Swedish language packs for boot and install time.
(My only concern is how to get the codecs on afterwards. But I can put an installer in place to add those.
I think a laptop should be able to play MP3s and DVDs. But I could add install-restricted-extras, for example,
which will require network. We can also pre-enable the medibuntu repistory so that installation is easy.)
I am a bit late in replying, because I do not actively follow all discussions, but since I made the Live CD I have some remarks
== Windows users ==
- virtualbox is not a solution. People running Windows usually have the
last version (not XP), which has the effect of taking all the RAM,
even on some not so old laptops. Adding a layer makes things worse.
- The .exe file that installs the live-cd on the hard disk of a
windows install does not work at all (tested on various machines
without success).
- Moreover there is no easy way for the participants to spread it
afterwards, you need a recent version of unetbootin or some
knowledge of sfdisk/hdparm/mkfs/syslinux to make it bootable to some
other key.
This is interesting. I compiled the latest live CD with SAGE_FAT_BINARIES=yes and SAGE_ATLAS_ARCH=base, but now I have a report that there are problems with sse2 instructions on an old computer.
HiI have an ISO installer image (Ubuntu + Sage) which I'd like to make available to the Sage community.
It is a 1.6G file created by UCK which I'd like to host on Sage servers, to preserve our institutional bandwidth.
This can be useful to anyone hosting or teaching a Sage workshop, or willing to install Ubuntu to get Sage.The installation procedure is trivial and easy, no different from a standard Ubuntu install:
http://www.ubuntu.com/download/help/install-desktop-long-term-support
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
Hi KCrisman,I'm not sure what Emil's ISO is. Is it a LIVECD only or an installer too? (The Ubuntu one is both.) Where can it be downloaded?
On 15 January 2013 16:36, kcrisman <kcri...@gmail.com> wrote:HiI have an ISO installer image (Ubuntu + Sage) which I'd like to make available to the Sage community.
It is a 1.6G file created by UCK which I'd like to host on Sage servers, to preserve our institutional bandwidth.
Great! Please let us know when it's been hosted so we can try it out!This can be useful to anyone hosting or teaching a Sage workshop, or willing to install Ubuntu to get Sage.The installation procedure is trivial and easy, no different from a standard Ubuntu install:
http://www.ubuntu.com/download/help/install-desktop-long-term-supportI assume this doesn't work as well (the "alongside your OS") on Mac? Wondering...Also, just out of curiosity, what are the differences with Emil's iso? I assume they each have their advantages and disadvantages.
Hi emil and thanks for your great job, I have used your previous sagelive and now I am managing to use your new one for my dissertation, 50 MB usage of RAM is very fantastic! However, I have also a question. I'm going to run my code on a quad-core machine with 18 GB of RAM, fortunately SageLive supports multicore but does it support also 18 GB of RAM? If not then do you have any suggestion? My code is so heavy that it failed on 4GB Mac Machine, now I want to use my professor's machine and I want to make sure it will work before to tell him I want to work on his machine.
Thanks again.
Right at the moment I see 4 projects maintained from this community with similar goals or structure:
1) Nicolas M. T's distro based on debian live
2) Jan Groenwalds distro based on Ubuntu
3) my SAGE Live CD distro based on Puppy Linux
4) the Fedora based image of Volker Braun to provide the base for the Sage virtual machine, this is maybe not geared toward a Live CD/or USB solution but still it is a complete custom linux distro including sage.
I'm really interested in a USB image that I can hand to students that want to do development with me that:
* I can modify (to include the Sage cell server, git, etc., for example)
* have all the development tools installed, so that Sage can easily be upgraded, rebuilt, etc.
* can have further things installed by users as needed
* can be installed to a hard disk if the student is interested
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+unsubscribe@googlegroups.com.
Regards,Hi Jason,No, I don't have an account. Yes, that would be reasonable from my side.
Jan
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Hi
Could the author of each LiveCD/USB image send a one or two-line description of it? Of when it is appropriate?Regards,
Size of image, Hardware Requirements (32/64 bit, resource requirements of desktop environment), languages, whether or not automatic updates if the installation is connected to a network.
Jan
--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To post to this group, send email to sage-...@googlegroups.com.
To unsubscribe from this group, send email to sage-devel+...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.