Please note that this FAQ also contains specific information that apply only to our pilot instance of ReCodEx at [MFF-UK](https://www.mff.cuni.cz/). If you have a specific problem with this instance, contact the administrator (`recodex@mff.cuni.cz`).
First, make sure you are using a modern web browser, preferably Mozilla Firefox or Google Chrome. Although our objective is to support all modern browsers, rapid development prevents us from doing extensive testing across many platforms; hence, we are sticking with the aforementioned two browsers for now.
Make sure you refresh your browser cache (`Ctrl+F5`) before logging in, especially if a new version has been deployed. The refresh will prevent older pieces of the application from lingering in your cache. This is just a precaution.
Sometimes a component on a page does not refresh itself correctly. The application is a complex system of components and is still under development. If you make an action and do not see the results in a reasonable while, refresh the page.
ReCodEx provides multiple ways for a user to register and log in. Currently there are two options: a **local** ReCodEx account or an account bound to the **CAS** service. The preferred way of registration and authentication is using the CAS service and using a local account only in special circumstances. CAS authentication provides more features, such as automatic binding of users to **SIS** groups. At present, the CAS registration is the only option enabled.
### I have successfully passed CAS authentication for the registration, but then I ran into an error
There are two most often errors. First one is that your LDAP data (in CAS service) do not contain email address (i.e., you will get `The user attributes received from the CAS do not contain an email address` error). In this case, the remedy should be simple enough. Just fill in you email address [in CAS administration](https://ldap1.cuni.cz/).
The second most frequent reason is that your account does not have appropriate affiliation attributes (`The user attributes received from the CAS has no affiliation attributes that would allow registration in ReCodEx. Authenticated account does not belong to a student not to an employee of MFF.`). In such case you should either attempt to set your LDAP records straight or (if you are not a regular student), ask the administrator to create you an account manually. We are planning a feature that will allow the teachers to send invitations to external users, but it will not be ready any time soon.
User can create local account in the profile **Settings** page. In here if you are registered using external account and not local one, you should see **Create local account** button. After clicking on it local login _without_ password will be created. Next thing you have to set your password to newly created local login.
### I registered (had created) a local account but I want to use also CAS and its advantages
The system's login mechanism is prepared for this option. The only prerequisite is that your email address in the local account must be the same as the one in CAS. If this is the case, binding the accounts is quite easy, just log in using CAS and the system will automatically bind those two accounts. Also please note that when binding your local account your password will be cleared and if you want to use it further, you have to change it.
In **C#** language there are none of the handy functions to operate with textual inputs like _scanf_ in **C**. Therefore for every C# build in ReCodEx there is [Reader.cs](https://github.com/ReCodEx/utils/blob/master/runners/cs/Reader.cs) library included to make life of C# programmers easier. Please note that library is suppose to work only with ASCII files and some difficulties can be observed with modern Unicode (UTF-8) encodings.
For some particular languages ReCodEx provides mappings of exit codes from internal runners to messages. Full tables of codes can be found on [separate page](https://github.com/ReCodEx/wiki/wiki/Exit-Code-Mappings).
Exercise and assignment are two terms which are not the same and there are some differences. In general, **exercises** are templates for **assignments**. In more detail, exercises are algorithmic problems defined and configured by supervisors. Exercise contains test cases which executes solutions submitted by users and check their outputs against sample results. Configuration of an exercise also defines time and memory limits which the solution has to meet and scoring details which are used in the evaluation (assigning points for passed tests). Exercise itself cannot be solved by students and is displayed only to supervisors and administrators.
If supervisor assigns an exercise to a group of students, an assignment is created from the exercise. Assignment can define some further details like number of points which can students gain or deadlines which should be met. But most importantly, an assignment is a full copy of the exercise. That means the assignment will not be modified when the configuration of the exercise is changed. This behavior was chosen to avoid unnecessary broken assignments in case the exercise is being edited (and possibly gets broken) by its author.
When the assignment gets out of sync with its original exercise (because the exercise was edited), a informational panel is displayed to the supervisor on the assignment detail/edit page. This panel also hold a button, which allows the supervisor to overwrite current assignment data (text, configuration, limits, ...) with the current version of the exercise.
## As a supervisor I want to see more detailed logs of user submissions
Before we start let us define **debug** vs. **normal** submissions. The results of a debug submission contain evaluation results, the execution log and the outputs of executed programs. And the results of a normal submission contain only the results needed for proper assignment of points (aka. evaluation results).
With this being said, all submissions made by students for an assignment are normal and even submissions of reference exercise solutions are normal. As a supervisor you should be able to do something called resubmitting of a user solution; this feature should be available on every page of a particular submission. On resubmitting, debug outputs and execution log are turned on by default and can be found in the results archive. Please note that resubmitting all solutions for an assignment is just a normal submission without debug information.
