Skip to content

Documentation for ISIMA/LIMOS Students✯

Working with Python on Pedagogy Servers✯

You have various Python labs, and to avoid library conflicts in your session, it's a good idea to work with virtual environments.

The Virtualenv tutorial is here

Installing a Linux Subsystem✯

With Windows 10, you can install a Linux subsystem without dual-booting.

The tutorial by Loic Yon is here

Communication with the ISIMA Discord SAV Bot✯

A Discord instance has been created for ISIMA students: discord.isima.fr

For all ISIMA students/staff✯

  • /email and /code: To start, you need to "connect" to access the entire server using the /email and /code commands. For each of the two previous commands, you do not need to enter any arguments (additional text). Simply enter the command and send it; a text field will appear at that moment!

  • /ticket create <required: summary> <required: category> <required: problem_type>: Now, to create a ticket for a request or problem, go to the #📝ticket channel and type /ticket create. At this point, three fields (arguments) need to be filled out to provide as much information as possible about your request/problem. First, a brief summary/title of your issue (try to be concise; this title will be the channel name, and you can elaborate further in the channel later). Second, a choice between "request", if you just have a question, or "incident", if you encountered a problem. Finally, a list of problem types (SSH, VPN, GitLab, TP Room, Personal VM, Personal Page, Printing, WiFi (Eduroam), Pedagogy Server (ADA), Personal Directory (home dir)). For WiFi and TP Room, after sending the command, one (location: where you are) or four (location, OS name, computer number, course name) additional fields will appear, respectively, so that CRI staff can better target your issue.

    Once done, the bot will create a channel with the information you provided, and a CRI staff member can process the request and respond in this channel. You can provide additional information as needed.

  • /ticket resolved: Finally, when a solution has been found, you or a CRI staff member can mark the ticket as resolved using /ticket resolved (if you find a solution yourself, please explain it before marking it as resolved).

Bonus: You can retrieve a collection of links with /lien, which might already help you!

For CRI Staff✯

In addition to the previous commands, you have access to a few extra commands to help with ticket management.

  • /ticket resolved: to mark a ticket as resolved, as for everyone (no arguments)
  • /ticket delete: to delete a ticket, which also removes it from the database (no arguments)

  • /ticket archive: to mark a ticket as archived, which moves it to the Archive category (no arguments)

  • /user | /user <optional: @mention>: to retrieve a user's email. Without the mention, you must be in the user's ticket to get their email.

  • /reload | /reload <optional: cogs>: to reload an extension if specified in the argument; otherwise, reloads all extensions.

  • /unload: to unload an extension (no arguments)

  • ,,eval: allows evaluating Python code. This command is not a slash command so that not everyone can see it, even if they don’t have the permissions to use it.