Official terminology of ReCodex which will be used in documentation and within code.
Official terminology of ReCodex which will be used in documentation and within code.
## WebApp (ReCodex)
## Web Application (web-app)
Graphical frontend of the whole ReCodex. This part is used by teachers and students.
Graphical frontend of the whole ReCodex. This part is used by teachers and students.
* **Exercise/Assignment** - Teachers are creating exercises which are solved by students. When exercise is solved then students submit their solution, this solution with all other informations (needed by worker) is called submission.
* **Exercise/Assignment** - Teachers are creating exercises which are solved by students. When exercise is solved then students submit their solution, this solution with all other informations (needed by worker) is called submission.
@ -14,7 +14,7 @@ Graphical frontend of the whole ReCodex. This part is used by teachers and stude
## QueueManager (ZeroMQ)
## QueueManager (ZeroMQ)
Handle incoming requests from php backend and forward them to actual workers, also handle answers from workers which has to be saved to the central database. (possibly files can be transfered through QM).
Handle incoming requests from php backend and forward them to actual workers, also handle answers from workers which has to be saved to the central database. (possibly files can be transfered through QM).
## Worker (IsoEval)
## Worker (recodex-worker)
Program which executes and evaluates tasks given by QM. Its internally divided into net part (communication with QM) and evaluation part which evaluates task itself.
Program which executes and evaluates tasks given by QM. Its internally divided into net part (communication with QM) and evaluation part which evaluates task itself.
* **Job** - Basically structure which is transfered from QM (Aka. one request from QM is job). Internally set of tasks. Job itself is transfered in form of configuration file written in YAML. Typicaly, job is one standard submission, but there could be also benchmarking submission for configuring limits of exercise or maybe submission for determining hardware and software configuration of given worker. This classification have no effect for evaluating the job.
* **Job** - Basically structure which is transfered from QM (Aka. one request from QM is job). Internally set of tasks. Job itself is transfered in form of configuration file written in YAML. Typicaly, job is one standard submission, but there could be also benchmarking submission for configuring limits of exercise or maybe submission for determining hardware and software configuration of given worker. This classification have no effect for evaluating the job.
Martin Polanka
8 years ago