September 2016 - tutorialcpp - mailman3.inf.ethz.ch

Einstiegstutorial Informatik I
by Oliver Kamer 21 Sep '16

21 Sep '16

Guten Abend Ich wollte mir gerade einmal das Einstiegstutorial für Informatik I anschauen, doch ich konnte es auf der Seite nicht finden. Der Link führt mich nur auf eine Seite wo ich mich für weitere Kurse anmelden kann. Kann es sein, dass der Kurs noch nicht online ist? Mit freundlichen Grüssen Oliver Kamer

2 1

FW: [E.Tutorial] Rückmeldung
by Hermann Lehner 19 Sep '16

19 Sep '16

-- Please reply above this line -- fyi Auf Fri, Sep 9 15:40:35 CEST 2016 schrieb: Absender: Sophie Heilmaier Nachricht: Es ist einfach und gut erklärt, es ist sehr klar, was zu tun ist. Die Fragen sind sehr gut zum Selbstfeedback. Es war nicht zu lange, also sehr schnell bearbeitet, es hat Spass gemacht. Einziger Vorschlag: Noch mehr Was gibt das Programm aus Beispiele(bissi mehr Übung wäre gut). Bei mir hat sich alles ohne Fehlermeldung öffnen lassen! Additional Data: - Name : C++ Grundlagen 1 - Lang : de - Tool : CodeBoard - EtID : YEZzzXxdShXZS6JNb {"TWDESKMessageId":"t!1110796!u166122!233381!8fcc4778-8ed9-44bc-97f6-dabb5dfa18a2*teamworkdesk!com"}

1 0

Fwd: [pele] [E.Tutorial] Rückmeldung #1123043
by Lehner Hermann 19 Sep '16

19 Sep '16

Feedback via Tool Begin forwarded message: From: <notifications(a)teamworkdesk.com<mailto:notifications@teamworkdesk.com>> Subject: [pele] [E.Tutorial] Rückmeldung #1123043 Date: 19 September 2016 at 16:33:39 GMT+2 To: Hermann Lehner <hermann.lehner(a)inf.ethz.ch<mailto:hermann.lehner@inf.ethz.ch>> Reply-To: " via Teamwork Desk" <ticket.1123043.233381.166122.olrxi5QCVL(a)teamworkdesk.com<mailto:ticket.1123043.233381.166122.olrxi5QCVL@teamworkdesk.com>> [https://ethz.teamwork.com/desk/images/email/arrow-tophead.png] Write ABOVE THIS LINE to post a reply [https://s3.amazonaws.com/tw-desk/i/233381/userimage/84284.20150911095245892…] Lukas assigned ticket #1123043<https://ethz.teamwork.com/desk/#/tickets/1123043> to you Customer: apraphae(a)student.ethz.ch<mailto:apraphae@student.ethz.ch> Notification Settings<https://ethz.teamwork.com/desk/#myprofile/notifications> [E.Tutorial] Rückmeldung [https://s3.amazonaws.com/tw-desk/i/233381/userimage/84284.20150911095245892…] Lukas assigned the ticket to Hermann Status: feedback [https://ethz.teamwork.com/desk/images/avatars/animals/sheep.png] Desk applied the trigger "Feedback" Status: feedback [https://ethz.teamwork.com/desk/images/avatars/animals/cat.png] asked Absender: Raphael Appenzeller Nachricht: Schritt 20/20: Forschlaufen: "Schreiben Sie das vorherige Programm so um, dass die Sie eine while anstelle eine forSchleife einsetzen." Hier ist ein "die" zu viel. Vielen Dank Additional Data: - Name : C++ Grundlagen 1 - Lang : de - Tool : CodeBoard - EtID : YEZzzXxdShXZS6JNb

1 0

Some more feedback
by Felix Friedrich 09 Sep '16

09 Sep '16

Dear all I made a mistake and did not see some of the feedback in the survey tool. Following I conclude what has not been mentioned before: (1) [german part] Rechtschreibfehler in Schritt 4: Konsole zeigt die >>die<< Ausgabe von Ihrem Programm und erlaubt Ihnen Eingaben vorzunehmen. (2) Slide 12: a year has 31536000 seconds, not only 525600 [--> would be minutes] (3) [german part] Grammatikfehler bei: Deklarieren Sie eine Variable vom Typ float welche ihren gegenwärtigen Vermögensstand repräsentiert (z. B. float money;) und lesen Sie >>einen<< reelle Zahl von der Eingabe in diese Variable ein. Danach rechnen Sie den Betrag nach einem Jahr aus und geben das Resultat aus. (4) More examples for converting while / for loops was on the wishlist of one of the students. [But we will repeat this in class anyways] One general remark was that the coloring of the answers in multiple choice questions was confusing. The student did not understand what becomes green and what becomes red. Maybe we should add one example at the very beginning to make that clear. Hermann told me that there is also feedback in the tutorial itself that we cannot see because we do not have the necessary access rights. He will report accordingly [and we should request that such information is open in future for the developers of tutorials]. Rgds Felix

2 1

Feedback Collection
by Felix Friedrich 08 Sep '16

08 Sep '16

Dear all, as promised here is the collection of student feedback regarding the tutorial. Unfortunately (but not really unexpectedly), not all students have yet filled in the C++ tutorial feedback (only 3). Not much statistics available. From the three students I "learn" that (a) Students have no or only very little experience with programming, consider themselves a bit better than average with working with the computers and have had about 1 year of Informatik courses at schools. (b) Parts 1 and 2 (Tutorial Overview / Expressions and Statements) of the tutorial were considered rather a bit too simple and between "boring" and "interesting but required". (c) Parts 3 and 4 (Variables and Numeric Operators) were considered interesting and exactly right in difficulty. (d) Part 5 (Control Structures) was considered very interesting and motivating and exactly right in difficulty. I think we should send the feedback form also to all other students when we invite them to the tutorial next week (!). Now some detailed feedbacks from the emails. This should be addressed before Monday: (1) On Slide 9: We did not distinguish between an "arithmetic expression" and and "expression". But we ask the students to count the number of arithmetic expressions. I suggest to introduce something like this: For the purpose of this tutorial, an arithmetic expression is either a primary expression of number type or a composite expressions involving one of the operators "+", "-", "/" and "%" and operands that themselves are arithmetic expressions. (2) On Slide 13: the Celsius to Fahrenheit program. We ask the students to look up the formula in the internet -- which I find a very good idea. However, they found the formula also as f = c * 1.8 + 32 and that does not provide the problem that we want them to observe. So, in this case we have to provide the formula. (3) On Slide 12 and 20: There are some return 0 missing in the code examples. Please make sure that all code examples contain return 0 in the main function. (4) On Slide 18: the age test is using age > 16 but indeed you are allowed to drink beer with 16. So it should be age >= 16 instead (5) In the beer related tasks the word "bier" appears instead of "beer". (6) The tutorial was not accessible via the ET homepage. This was intended for now but it should be accessible to the students (and, basically, the public with ETH access) from next week. Please don't forget to mirror any changes in the repo. Suggestion: Change the original and when finished copy the text into the file and SVN commit. Best Felix

2 1

Verständnisfrage
by Alessandro Scozzafava 06 Sep '16

06 Sep '16

Bei Schritt 9. Frage 1: Wie viele arithmetische Ausdrücke hat folgende Anweisung? std::cout << 4 + 2 << " " << 3 * 8 << std::endl; std::cout << 6 / 5 + 13 << " " << 1 + 9 * 11 << std::endl; Sind mit "arithmetische Ausdrücke" alle Ausdrücke gemeint (auch Primärausdrücke) oder nur Ausdrücke mit mathematischen Operatoren? Wenn ja, was ist die Definition eines arithmetischen Ausdruckes bzw. ab wann gilt ein Ausdruck arithmetisch? Gruss Alessandro Scozzafava

2 1

C++ Tutorial Informatik I
by Graf Melanie 05 Sep '16

05 Sep '16

Sehr geehrter Herr Gärtner, Herr Lehner und Herr Friedrich Ich habe das C++ Tutorial jetzt durchgearbeitet und alles sehr gut verstanden. Einige kleine Fragen bleiben jedoch. Die erste ist bei Schritt 13/20 die Celsius Aufgabe: Ich habe dort die Formel °F = °C * 1.8 + 32 im Internet gefunden und das Programm folgendermassen geschrieben: #include <iostream> int main() { int celsius; std::cout << "Type the temperature in °C" << std::endl; std::cin >> celsius; std::cout << celsius << "°C are " << celsius * 1.8 + 32 << "°F" << std::endl; return 0; } bei diesem Programm bekam ich dann das Resultat 87.8°F anstatt 87°F, celsius wurde ja als integer gespeichert. Liegt das an der Formel, die 1.8 beinhaltet? Die nächste Frage wäre noch bei Schritt 12/20 und Schritt 17/20 jeweils bei dem ersten Code, den man öffnet, wurde am Schluss nicht return 0; geschrieben. Hat das einen bestimmten Grund oder wurde das einfach vergessen? Und die letzte Frage wäre bei Schritt 18/20. Dort wird bei den Lösungen zum Programm if(age > 16)geschrieben. Wenn man also 16 als Alter eingibt erscheint „You cannot get beers. Please come back when you're 16 or older!“ müsste es nicht if(age >= 16)heissen? (Bei der nächsten Aufgabe bei Schritt 18/20 mit den Variablen money und beers wird auch wieder if(age > 16)auf Zeile 9 geschrieben.) Bei den Bier Aufgaben wurde in den geöffneten Codes jeweils allgemein „here are your … biers. Your have … CHF left.“ geschrieben, was nichts am Verständnis ändert, wollte es nur mal kurz anmerken. Freundliche Grüsse Melanie Graf

2 1

C++ Tutorial
by Schulz Fiammetta 05 Sep '16

05 Sep '16

Guten Morgen ich möchte gerne das C++ Tutorial lösen, allerdings ist es nicht online. Nur die beiden Java, Python, Lattex und Matlab. Vielen Dank für Ihre Hilfe und mit freundlichen Grüssen F. Zanazzi

2 2

Re: [Tutorialcpp] Testers informed, Repository
by Felix Friedrich 05 Sep '16

05 Sep '16

Dear Luka thanks for the feedback: indeed I had provided access only to the subfolder cpp. Sorry for the confusion. I have now provided the correct access and thus it should work now. Rgds Felix On 05.09.2016 10:39, Luka Malisa wrote: > Dear Felix, > > hm...I can’t access the repo. It says “Forbidden” when I login with my > eth login. > > Luka > >> On Sep03 2016, at 15:33, Felix Friedrich <felix.friedrich(a)inf.ethz.ch >> <mailto:felix.friedrich@inf.ethz.ch>> wrote: >> >> Dear all >> >> as you have seen: I have sent out the invitation to students (only >> six, for now) to help with testing the online tutorial. >> >> I have hesitated a bit because not all of us (but me) have yet done a >> final pass over the whole thing. But I think it is in a shape that >> will certainly not make a bad impression with the testers. And better >> find the bugs early than with all of the students. >> >> I have made another pass over the tutorial and have patched minor issues. >> >> *Repository*: I have copied the content to text-files that now reside >> in our repository at >> https://svn.inf.ethz.ch/svn/lecturers/vorlesungen/trunk/tutorials >> (all of you have RW access). *Further changes **should be made >> visible there *by simply copying the content of the respective >> chapter into the text-file and submitting it to the repo. Therewith >> we can now avoid issues with losing content, which, by the way, now >> happened just before I put the things to the repo. Moreover, we can >> keep track of what changed. Most of my changes from today are >> documented this way now, for instance. >> >> Thanks all of you for your efforts, in particular for helping last >> minute today! >> >> Best Regards >> >> Felix >> >> >> _______________________________________________ >> tutorialcpp mailing list >> tutorialcpp(a)lists.inf.ethz.ch <mailto:tutorialcpp@lists.inf.ethz.ch> >> https://lists.inf.ethz.ch/mailman/listinfo/tutorialcpp >

1 0

Testers informed, Repository
by Felix Friedrich 03 Sep '16

03 Sep '16

Dear all as you have seen: I have sent out the invitation to students (only six, for now) to help with testing the online tutorial. I have hesitated a bit because not all of us (but me) have yet done a final pass over the whole thing. But I think it is in a shape that will certainly not make a bad impression with the testers. And better find the bugs early than with all of the students. I have made another pass over the tutorial and have patched minor issues. *Repository*: I have copied the content to text-files that now reside in our repository at https://svn.inf.ethz.ch/svn/lecturers/vorlesungen/trunk/tutorials (all of you have RW access). *Further changes **should be made visible there *by simply copying the content of the respective chapter into the text-file and submitting it to the repo. Therewith we can now avoid issues with losing content, which, by the way, now happened just before I put the things to the repo. Moreover, we can keep track of what changed. Most of my changes from today are documented this way now, for instance. Thanks all of you for your efforts, in particular for helping last minute today! Best Regards Felix

1 0