Skip to content

Documentation for ISIMA/LIMOS students✯

Working with Python on pedagogical servers✯

You have various Python practical works (TPs). To avoid library conflicts in your session, it is recommended to work with virtual environments.

The tutorial on Virtualenv is here

Installing a Linux subsystem✯

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

The tutorial created 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 must "connect" to gain access to the entire server using the /email and /code commands. For both of the 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>: To create a ticket for a request or issue, go to the #📝ticket channel and enter /ticket create. At this point, three fields (arguments) must be filled out to provide maximum information about your request/issue. First, a brief summary/title of your problem (try to be concise, as this title will be the channel name; you can elaborate further in the channel later). Second, a choice between "request" if you 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), Pedagogical 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, to help the CRI staff better target your issue.

    Once completed, 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 may need to 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 that may already help you!

For CRI staff✯

In addition to the previous commands, you have access to a few extra commands to assist 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 as an argument; otherwise, reloads all extensions.

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

  • ,,eval: allows evaluating Python code. This command is not a slash command to prevent everyone from seeing it, even if they lack permissions to use it.