Sagedays90.jpg

Target Audience

This conference is aimed at women at all career stages who are interested in using or developing for Sage. Undergraduate, graduate, postdoc, and faculty are welcome to apply. We will take time at the workshop to teach the basics of Sage development; it is not required that you are an experienced developer. We are especially hoping to include women who have never attended SageDays. Applications are now closed.

Schedule:

The schedule with room numbers can be found here.

SageDays90Photo.jpg

Projects

Renata dealt with two of the tickets, #22073 and #20439. At the moment the first one has a positive review and the second needs_work. Wish list:

Tickets

Please add #sd90 to any tickets you are working on on trac. If your ticket needs review, added it to the list on the tickets page to advertise.

Accommodations:

Travel:

The k8s server

William Stein has kindly provided a server for us to use during the workshop, with 48 CPUs and 256 GB of RAM. It is running CoCalc, so you can access it from your browser.

Creating an Account

You should create an account here. You will need a secret token, which will be e-mailed to participants (ask Ursula Whitcher (uaw@umich.edu) if you can't find it). Once you have an account, someone will have to add you to the Sage Days 90 project; anyone who is already part of the project can do so from the project settings page. At that point, you will be able to access the server at k8s.sagemath.org.

Git

If you will be doing Sage development, you need to set up a terminal that knows who you are (since we're all using the same user when we log in from the browser). This way we will be able to share Sage installations on the server.

If you provided your trac username to Ursula Whitcher (uaw@umich.edu), the setup has been done for you. Otherwise, open up a terminal (~/Terms/Admin.term exists for this purpose) and run the script setup_user (from anywhere). This will ask you some questions (name, e-mail, trac account info) and create a terminal for you (~/Terms/$TRAC_USERNAME.term). If you're ever interacting with git, you should use this terminal (or the ssh method described below) so that git knows who you are.

Trac Passwords

You have the option of storing your trac password (in a plain text file on the server, so don't do so if your trac password is sensitive). You can control how your trac password is handled by the scripts set_trac_password and unset_trac_password from your terminal. If you don't store your trac password in a file, you will be prompted for it when you open your terminal.

Editor

When you make a git commit, you can specify the commit message on the command line with the -m flag. Otherwise, git will open an editor for you to enter the commit message. The default editor is vim. If you would rather use a different editor (such as emacs), you can set your editor by running the set_editor script in your terminal.

Updating Sage to 8.1.beta9

To update your version of Sage on k8s, type in your term:

git checkout develop

git pull --ff-only trac develop

make build

SSH

SSHing into the project

Instead of using the browser, you can also SSH into the project and work in a terminal on your laptop.

Once you add the public key from your laptop (generated by ssh-keygen and then copied from ~/.ssh/id_rsa.pub for example) to ~/authorized_keys in the browser, you will be able to SSH into the project using the following command.

ssh XXX@k8s-ssh.sagemath.org -p 2222

At the beginning of your key in ~/authorized_keys on the server you should add command=".init_user roed"  for example. You can look at the other keys there for examples.

Setting up SSH keys for trac

If you want to be able to push changes to trac, you need to upload your key from the k8s server to trac. You can find your ssh key by running show_ssh_key in your terminal.

Sage installations

If you provided your trac username to Ursula Whitcher (uaw@umich.edu), you should have a Sage install in ~/Src. If not, you can create a new Sage installation for yourself by running 

new_sage

at your command prompt, or new_sage $YOUR_TRAC_USERNAME at any prompt (replacing $YOUR_TRAC_USERNAME with your trac username. Note that this will take some time, since it must build Sage (though the build runs in parallel and doesn't need to build spkgs).

The setup described above also means that the sage command in your terminal will be aliased to your copy of Sage.

Building and Large output

Avoid sending huge amounts of output in a terminal, as this slows the whole project down for everybody (proper output truncation isn’t sufficiently implemented). Here are some options to avoid this.

1. When building Sage, you can do 

./sage -b > output 2>&1

rather than just sending a large amount of output to your terminal. You can check on output by typing 

tail output

2. If you know tmux, do control+b, then c to make a new session, and leave the large-output session in a different session. You can switch back and forth with control+b then n.

3. If you've set up your terminal as described above, then 

make build

in your sage folder will do the redirection for you, as well as automatically use many threads (so that the build goes much faster).

Some Guides For Getting Started With SAGE

Mailing Lists and Resources

Organizers:

days90 (last edited 2017-10-27 00:51:36 by alina)