From 1907976b41c82bd775d0dc9a9286d07651078c85 Mon Sep 17 00:00:00 2001 From: adjoly Date: Sun, 12 Oct 2025 20:37:45 +0200 Subject: [PATCH] =?UTF-8?q?=E3=80=8C=F0=9F=8F=97=EF=B8=8F=E3=80=8D=20wip:?= =?UTF-8?q?=20work=20in=20progress,=20not=20done=20yet.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/lescrampte/corr/abstract-vm/index.html | 720 +++++++++++++++++++++ src/lescrampte/corr/dslr/index.html | 511 +++++++++++++++ src/lescrampte/index.html | 6 + 3 files changed, 1237 insertions(+) create mode 100644 src/lescrampte/corr/abstract-vm/index.html create mode 100644 src/lescrampte/corr/dslr/index.html diff --git a/src/lescrampte/corr/abstract-vm/index.html b/src/lescrampte/corr/abstract-vm/index.html new file mode 100644 index 0000000..f386ef9 --- /dev/null +++ b/src/lescrampte/corr/abstract-vm/index.html @@ -0,0 +1,720 @@ + + + + + + + + + + + + + + + +Intra Projects abstract-vm Edit + + + + +
+
+
+

+Scale for project abstract-vm +

+
+
+

Introduction

+

+
Please respect the following rules:

- Remain polite, courteous, respectful and constructive
throughout the correction process. The well-being of the community
depends on it.

- Identify with the person (or the group) graded the eventual
dysfunctions of the work. Take the time to discuss
and debate the problems you have identified.

- You must consider that there might be some difference in how your
peers might have understood the project's instructions and the
scope of its functionalities. Always keep an open mind and grade
him/her as honestly as possible. The pedagogy is valid only and
only if peer-evaluation is conducted seriously.
+

+
+
+

Guidelines

+

+
- Only grade the work that is in the student or group's
GiT repository.

- Double-check that the GiT repository belongs to the student
or the group. Ensure that the work is for the relevant project
and also check that "git clone" is used in an empty folder.

- Check carefully that no malicious aliases was used to fool you
and make you evaluate something other than the content of the
official repository.

- To avoid any surprises, carefully check that both the correcting
and the corrected students have reviewed the possible scripts used
to facilitate the grading.

- If the correcting student has not completed that particular
project yet, it is mandatory for this student to read the
entire subject prior to starting the defence.

- Use the flags available on this scale to signal an empty repository,
non-functioning program, a norm error, cheating etc. In these cases,
the grading is over and the final grade is 0 (or -42 in case of
cheating). However, with the exception of cheating, you are
encouraged to continue to discuss your work (even if you have not
finished it) in order to identify any issues that may have caused
this failure and avoid repeating the same mistake in the future.
+

+
+ +
+
+

Attachments

+
+
+ +
+
+

+ +subject.pdf +

+
+
+ +
+ +
+
+
+
+

Preliminaries

+

+
+

Preliminaries tests

+

+

Check firstly the following elements :

+ +
    +
  • There is something in the git repository.
    • +
  • No cheating (All functions are authorised, the student can explain +the code)
    • +
+ +

If an element isn't implemented as explained in the subject, the
+ grading ends. Use the appropriate flag. You're allowed to debate
+ some more.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

Feature's testing

+

+
+

Test 1

+

+

Run the following program :

+ +

\r\n\r\npush int32(42)\r\npush int32(33)\r\nadd
+;poney\r\npush float(44.55)\r\nmul\r\npush double(42.42)\r\n;commentaire
+de ouf\r\npush int32(42)\r\ndump\r\npop\r\nassert double(42.42)\r\nexit\r\n\r\n

+ +

Does the program execute properly?\r\n

+ +

+
+ + +
+ + + + +
+
+

Test 2

+

+

Run the following program :

+ +

\r\n\r\npush int32(32)\r\npush int32(0)\r\ndiv\r\nexit\r\n\r\nDoes
+the program stops properly because of the 0 division?\r\n

+ +

+
+ + +
+ + + + +
+
+

Test 3

+

+

Run the following program:
+ \r\n\r\npush int16(999999999999999999999999999)\r\nexit\r\n\r\n
+ Does the program stops properly because of the overflow error?\r\n"

+ +

+
+ + +
+ + + + +
+
+

Test 4

+

+

Run the following program:
+ \r\n\r\npush int16(32 ;)\r\npu int(32))\r\nexit\r\n\r\nDoes
+ the program stops properly because of a syntax error?\r\n"

+ +

+
+ + +
+ + + + +
+
+

Test 5

+

+

Run the following program:
+ \r\n\r\npop\r\nexit\r\n\r\n Does the
+ program stops properly because of an empty stack?\r\n"

+ +

+
+ + +
+ + + + +
+
+

Test 6

+

+

Run the following program:
+ \r\n\r\npush int32(42)\r\nassert int32(0)\r\nexit\r\n\r\nDoes
+ the program stops properly on an assert error?\r\n"

+ +

+
+ + +
+ + + + +
+
+

Test 7

+

+

Run the following program:
+ \r\n\r\npush int32(42)\r\nadd\r\nexit\r\n\r\n
+ Does the program stops properly on a missing operand?\r\n"

+ +

+
+ + +
+ + + + +
+
+

Test 8

+

+

Run the following program:
+ \r\n\r\npush int8(33) ;!\r\npush int8(112)
+ ;p\r\npush int8(111) ;o\r\npush int8(108) ;l\r\npush int8(112) ;p\r\nprint\r\npop\r\nprint\r\npop\r\nprint\r\npop\r\nprint\r\npop\r\nprint\r\npop\r\nexit\r\n\r\n
+ Does the program run properly and display the following output?\r\n\r\np\r\nl\r\no\r\np\r\n!\r\n\r\n"

+ +

+
+ + +
+ + + + +
+
+

Custom test

+

+

Run your own tests. For example, run operation with mixed types, really
+big or really small numbers (overflow and underflow excluded).

+ +

Does the program run as expected?

+ +

+
+ + +
+ + + + +
+
+

Difficult custom test

+

+

Run a really complicated program of your invention (a vicious test
+basically).

+ +

Does the program run as expected?

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

Implementation

+

+
+

Inputs

+

+

The VM must be able to read either from a file or from the standard input
+(with a ;; to end the input)

+ +

+
+ + +
+ + + + +
+
+

Stack

+

+

The VM countains a "stack". It can't be a std::stack except if
+rigorously justified (std::stack isn't iterable, it can at best
+be used as a base class).

+ +

+
+ + +
+ + + + +
+
+

Polymorphic operands

+

+

Are operand manipulated polymorphicaly through IOperand *.
+If not, the project is off topic. Click on the "crash" flag,
+the grading stops but you're allowed to debate some more.

+ +

+
+ + +
+ + + + +
+
+

Operand factory

+

+

There must be an operand "factory" implementing the following function:
+IOperand * SomeClass::createOperand(eOperandType type, const std::string & value);

+ +

+
+ + +
+ + + + +
+
+

Precision management

+

+

The VM manages precision in a non trivial way - An if forest or any
+other disgusting thing. An enum is totally acceptable for example.

+ +

+
+ + +
+ + + + +
+
+

Parser

+

+

The VM has a clean and clomplete parsing?

+ +

+
+ + +
+ + + + +
+
+

Exceptions

+

+

The VM must use exceptions to manage errors.

+ +

Select the corresponding grade:

+ +
    +
  • No exceptions: 0
    • +
  • Scalar exceptions (string, char*, int, ...): 1
    • +
  • Use of pre-made exceptions (only std::exception ou autre): 2
    • +
  • Use of custom exceptions custom inheriting from std::exception: 3
    • +
  • Use of custom exceptions custom inheriting from a more specific class than std::exception: 4
    • +
+ +

+
+ + +
Rate it from 0 (failed) through 5 (excellent)
+
+
+
+
+
+
+
+

Bonus

+

+
+

Complete verification

+

+

The VM is capable of ouputing every error in a file, and doesn't
+stop at the first error met (interpretation excluded).

+ +

+
+ + +
+ + + + +
+
+

Advanced parsing

+

+

The parsing is well structured, more specificaly a lexer / parser combo
+with well defined roles as it should be in reality.

+ +

+
+ + +
+ + + + +
+
+

Other bonus

+

+

Count in this section the different bonuses. You can grade up to 5
+distinctive bonuses.

+ +

Each bonus must be :

+ +
    +
  • At the very least useful (up to you)
    • +
  • Well implemented and 100% functional
    • +
+ +

+
+ + +
Rate it from 0 (failed) through 5 (excellent)
+
+
+
+
+
+
+
+

Ratings

+

Don’t forget to check the flag corresponding to the defense

+
+ + +
+
+ + + + + + + + + +
+
+ +
+
+

Conclusion

+ +
+

Leave a comment on this evaluation ( 2048 chars max )

+ + +
+ +
+
+ +
+
+ +
+
+ + + + + + + + + +
+ + + + + + + + + + + diff --git a/src/lescrampte/corr/dslr/index.html b/src/lescrampte/corr/dslr/index.html new file mode 100644 index 0000000..2cf6d0e --- /dev/null +++ b/src/lescrampte/corr/dslr/index.html @@ -0,0 +1,511 @@ + + + + + + + + + + + + + + +Intra Projects dslr Edit + + + +
+
+
+

+Scale for project dslr +

+ +
+
+

Introduction

+

+
For the smooth running of this evaluation, please respect the following rules:

- Remain polite, kind, respectful and constructive whatever happens during
this conversation. It's a matter of confidence between you and the
42 community.

- Highlight the potential problems you ‘ve had with the work you're presented
to the person or the group you're grading, and take the time to talk about
and discuss those issues.

- Accept the fact that the exam subject or required functions might lead
to different interpretations. Listen to your discussion partner's
perspective with an open mind (are they right or wrong ?) and grade them as
fairly as possible.
42's teaching methods can make sense only if peer-evaluation is
taken seriously.
+

+
+
+

Guidelines

+

+
- You must only evaluate what you will find in the student's or group's
GiT repository.

- Take the time to check that the GiT repository matches the student or
group and the project.

- Double check that no malicious alias was used to mislead you and make you
grade something different from the official repository content.

- If a script supposed to help evaluate the exam is supplied by either side, the
other side will have to strictly check it to avoid nasty surprises.

- If the evaluating student has not yet taken this project, they will have to
read the exam subject in its entirety before starting the evaluation.

- Use the flags available on this grading system to signal an empty or non-
funcional project, a norm flaw, cheating, etc. In that case, evaluation stops
and final grade is 0 (or -42 if it's a cheating problem). However, if it's
not a cheating problem, you are invited to keep talking about the work that
has been done (or not done, as a matter of fact) in order to identify the
issues that lead to this stalemate and avoid it next time.
+

+
+ +
+
+

Attachments

+
+
+

+ +evaluate.py +

+
+
+

+ +dataset_truth.csv +

+
+
+ +
+
+

+ +subject.pdf +

+
+
+

+ +datasets.tgz +

+
+
+ +
+ +
+
+
+
+

Data analysis

+

+In this part, we will study the succinct data analysis through the 'describe' +function. +

+
+

The describe function

+

+

Execute the 'describe' function with 'dataset_train.csv' in parameter. Does
+the output respect the requirement of the subject? That is: count, mean,
+std, min, 25%, 50%, 75% and max.

+ +

+
+ + +
+ + + + +
+
+

Hands in code

+

+

Open the 'describe' source and talk about the code together. Make sure the
+assessed student doesn't use any third party library that would replace
+one of the requested results. For instance: no 'mean' function prompting
+the student would not have coded himself.

+ +

If the assessed student is using a prohibited function, check the Cheat
+flag and end the evaluation. Validate only if they coded everything
+themselves.

+ +

+
+ + +
+ + + + +
+
+

Notions explanations

+

+

Ask the assessed student to explain the following notions:

+ +
    +
  • What is the average (mean)?
    • +
  • What is the standard deviation (std)?
    • +
  • What is a quartile (25% - 50% - 75%)?
    • +
+ +

1 correct answer = 1 point, 2 correct answers = 3 points, 3
+correct answers = 5 points.

+ +

+
+ + +
Rate it from 0 (failed) through 5 (excellent)
+
+
+
+
+
+
+
+

Data visualization

+

+Here, we're going to tackle data visualization. This section will require +a little thinking more than just development skills. You will be the one to +judge if the assessed student answers the question and if his explanations +are satisfying. + +If you're not satisfied with an answer, it might be wise to sit and think of +another solution together. + +There might be more than one anwser to a given question. +

+
+

Histogram

+

+

Launch the histogram script.

+ +

Does the displayed graphic help you answer the question:
+Which Hogwarts class has an homogenous grade repartition between the four
+houses?

+ +

Ask the assessed student to explain what you see and why they believe it
+answers the question.

+ +

+
+ + +
+ + + + +
+
+

Scatter plot

+

+

Launch the scatter_plot script.

+ +

Does the displayed graphic help you answer the question:
+which two features are similar?

+ +

Ask the assessed student to explain what you see and why they believe it
+answers the question. For this part, there should only be one obvious
+answer.

+ +

+
+ + +
+ + + + +
+
+

Pair plot

+

+

Launch the pair_plot script.

+ +

Does the graphic help you answer the question:
+from this graph, which characteristics will you use to train your coming
+logistic regressions?

+ +

Ask the assessed student to explain what you see and why they believe it
+answers the question.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

Logistic regression

+

+We are going to evaluate the multi-classifier. +

+
+

Discussions

+

+

Before launching any program, ask the assessed student how the logistic
+regression works.

+ +

We're not here to nitpick but to make sure the assessed student has
+understood the following points: how logistic regression works compared to
+to linear regression, point in nornmalising the data, what's the one-vs-all
+method. Of course, you can go further than these elements, but don't try
+to push or trick the student.

+ +

Did the student give the correct explanations?

+ +

+
+ + +
+ + + + +
+
+

Machine learning!

+

+

Time to evaluate the algorithme. First, execute logreg_train with
+dataset_train.csv. This should create a file containing the weights for
+each model. Is this the case?

+ +

+
+ + +
+ + + + +
+
+

Predictions

+

+

Once you have trained your models, execute logreg_predict with the
+weights and dataset_test.csvas parameters. This should create a file
+named houses.csv.

+ +

In order to evaluate the multi-classifier performance, use the script
+evaluate.py which will compare the files houses.csv with
+dataset_truth.csv containing the truth (that is, the real houses
+the students belong to).

+ +

Mc Gonagall had asked for a minimum score of 98% (equals 0.98). If this is
+so, you can validate. Otherwise... Too bad.

+ +

+
+ + +
+ + + + +
+
+
+
+
+
+

Bonus

+

+Reminder: if, somehow, the program doesn't react as it should (bus error, +segfault etc...), evaluation ends and the grade is 0. Use the respective +flags. This instruction works during the whole evaluation. + +Bonus will be taken into account only if the mandatory part is PERFECT. +PERFECT meaning it is completed, that its behavior cannot be faulted, even +because of the slightest mistake, improper use, etc... Practically, it +means that if the mandatory part is not validated, none of the bonus will +be taken in consideration. +

+
+

Let's talk, now.

+

+

Feel free to grade any additionnal features in the project. It will
+remain at your discretion as long as you have good reasons to do so.

+ +

+
+ + +
Rate it from 0 (failed) through 5 (excellent)
+
+
+
+
+
+
+
+

Ratings

+

Don’t forget to check the flag corresponding to the defense

+
+ + +
+
+ + + + + +
+
+ +
+
+

Conclusion

+ +
+

Leave a comment on this evaluation ( 2048 chars max )

+ + +
+ +
+
+ +
+
+ +
+
+ + + + + + + + + +
+ + + + + + + + + + + diff --git a/src/lescrampte/index.html b/src/lescrampte/index.html index a5c3a63..9f6a651 100644 --- a/src/lescrampte/index.html +++ b/src/lescrampte/index.html @@ -87,6 +87,12 @@ avaj-launcher + + abstract-vm + + + dslr +