studium 0.13.1
Sign up to get free protection for your applications and to get access to all the features.
Potentially problematic release.
This version of studium might be problematic. Click here for more details.
- checksums.yaml +7 -0
- data/README.md +2785 -0
- data/bin/ask_exam_question +7 -0
- data/bin/check_description_of_these_lectures +7 -0
- data/bin/curriculum_module_displayer +7 -0
- data/bin/cycle +7 -0
- data/bin/d10 +7 -0
- data/bin/d100 +7 -0
- data/bin/d15 +7 -0
- data/bin/d20 +7 -0
- data/bin/d25 +7 -0
- data/bin/d3 +7 -0
- data/bin/d30 +7 -0
- data/bin/d5 +7 -0
- data/bin/determine_curricula +7 -0
- data/bin/display_lecture_url +7 -0
- data/bin/exam_registration_at +7 -0
- data/bin/exam_statistics +7 -0
- data/bin/exams_per_month +9 -0
- data/bin/finished_exams_at_this_university +7 -0
- data/bin/flashcards +7 -0
- data/bin/from_curriculum_id_to_university +9 -0
- data/bin/location_to_this_exam_topic.rb +7 -0
- data/bin/mandatory_continuous_assessment +7 -0
- data/bin/mandatory_upcoming_courses +7 -0
- data/bin/n_ECTS +7 -0
- data/bin/n_exam_questions_already_answered +16 -0
- data/bin/nquestions +7 -0
- data/bin/nsolved +7 -0
- data/bin/open_last_exam_question_asked_file +7 -0
- data/bin/passed_exams +7 -0
- data/bin/passed_pr/303/274fungsimmanente_courses +7 -0
- data/bin/pdf_for +7 -0
- data/bin/random_exam_topic +7 -0
- data/bin/report_solved_topics +7 -0
- data/bin/return_n_ects_from_this_file +7 -0
- data/bin/search_for_n_ects +7 -0
- data/bin/show_lectures_on_the_commandline +7 -0
- data/bin/show_themes +7 -0
- data/bin/solved +9 -0
- data/bin/solved_ects +7 -0
- data/bin/studienkennzahl +7 -0
- data/bin/studium +7 -0
- data/bin/studium_skeleton +7 -0
- data/bin/ufind +7 -0
- data/bin/upcoming_exams +7 -0
- data/bin/week_parser +7 -0
- data/doc/ECTS_CONSIDERATIONS.md +81 -0
- data/doc/HOW_TO_DETERMINE_WHICH_PART_IS_THE_QUESTION_AND_WHICH_PART_IS_THE_ANSWER.md +44 -0
- data/doc/README.gen +2742 -0
- data/doc/SQL_database_specification.md +46 -0
- data/doc/deprecated_components.md +24 -0
- data/doc/documentation_for_the_file_lecture_information.md +311 -0
- data/doc/elegant_colours.md +21 -0
- data/doc/todo/TODO_FOR_STUDIUM_GEM.md +112 -0
- data/doc/todo/TODO_FOR_THE_GRAPHICAL_PARTS_OF_THE_STUDIUM_GEM_INCLUDING_WWW_RELATED_ASPECTS.md +35 -0
- data/img/STUDIES.png +0 -0
- data/lib/studium/autoinclude.rb +7 -0
- data/lib/studium/base/base.rb +2710 -0
- data/lib/studium/base/prototype.rb +543 -0
- data/lib/studium/c/README.md +2 -0
- data/lib/studium/c/a.out +0 -0
- data/lib/studium/c/obtain_random_entry.c +11 -0
- data/lib/studium/check_and_sanitize/README.md +11 -0
- data/lib/studium/check_and_sanitize/check_curriculum_for_correct_separation_of_bachelor_and_master.rb +141 -0
- data/lib/studium/check_and_sanitize/check_for_all_exam_topics_being_registered.rb +110 -0
- data/lib/studium/check_and_sanitize/check_for_correct_themes_of_each_course.rb +90 -0
- data/lib/studium/check_and_sanitize/check_for_existing_description_of_this_lecture.rb +189 -0
- data/lib/studium/check_and_sanitize/check_the_lecture_information_file.rb +163 -0
- data/lib/studium/check_and_sanitize/find_duplicate_lectures.rb +115 -0
- data/lib/studium/check_and_sanitize/missing_priority_entry.rb +44 -0
- data/lib/studium/check_and_sanitize/sanitize_this_string_containing_the_lva_dates.rb +79 -0
- data/lib/studium/colours/colours.rb +549 -0
- data/lib/studium/colours/sfancy.rb +46 -0
- data/lib/studium/colours/sfile.rb +35 -0
- data/lib/studium/colours/simp.rb +40 -0
- data/lib/studium/colours/use_colours.rb +39 -0
- data/lib/studium/colours/use_this_colour_for_exam_questions_and_exam_answers.rb +80 -0
- data/lib/studium/commandline/commandline.rb +932 -0
- data/lib/studium/commandline/menu.rb +903 -0
- data/lib/studium/constants/colours.rb +14 -0
- data/lib/studium/constants/constants.rb +2142 -0
- data/lib/studium/constants/image_constants.rb +217 -0
- data/lib/studium/constants/web_constants.rb +25 -0
- data/lib/studium/css/project.css +267 -0
- data/lib/studium/curricula/curriculum.rb +210 -0
- data/lib/studium/curricula/curriculum_as_string.rb +280 -0
- data/lib/studium/curricula/curriculum_module_displayer/constants.rb +33 -0
- data/lib/studium/curricula/curriculum_module_displayer/curriculum_module_displayer.rb +417 -0
- data/lib/studium/curricula/curriculum_module_displayer/initialize.rb +25 -0
- data/lib/studium/curricula/curriculum_module_displayer/menu.rb +45 -0
- data/lib/studium/curricula/curriculum_module_displayer/reset.rb +74 -0
- data/lib/studium/curricula/curriculum_module_displayer/run.rb +20 -0
- data/lib/studium/curricula/curriculum_module_displayer/set_use_this_curriculum.rb +93 -0
- data/lib/studium/curricula/curriculum_module_displayer/show_and_report.rb +190 -0
- data/lib/studium/curricula/determine_curricula/constants.rb +11 -0
- data/lib/studium/curricula/determine_curricula/determine_curricula.rb +36 -0
- data/lib/studium/curricula/determine_curricula/help.rb +39 -0
- data/lib/studium/curricula/determine_curricula/initialize.rb +48 -0
- data/lib/studium/curricula/determine_curricula/menu.rb +151 -0
- data/lib/studium/curricula/determine_curricula/misc.rb +403 -0
- data/lib/studium/curricula/determine_curricula/report.rb +143 -0
- data/lib/studium/curricula/determine_curricula/reset.rb +59 -0
- data/lib/studium/curricula/determine_curricula/run.rb +19 -0
- data/lib/studium/curricula/determine_elective_courses_in_this_curriculum.rb +112 -0
- data/lib/studium/curricula/display_bachelor_curricula.rb +90 -0
- data/lib/studium/curricula/mitteilungsbl/303/244tter/mitteilungsbl/303/244tter.rb +324 -0
- data/lib/studium/curricula/modules/display_on_the_commandline.rb +319 -0
- data/lib/studium/curricula/modules/return_n_ects_in_this_module.rb +75 -0
- data/lib/studium/curricula/n_percent_solved_in_this_curriculum.rb +75 -0
- data/lib/studium/curricula/prepare_individual_curriculum.rb +304 -0
- data/lib/studium/curricula/random_curriculum_creator/random_curriculum_creator.rb +163 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum.rb +114 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/constants.rb +11 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/initialize.rb +27 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/menu.rb +35 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/misc.rb +264 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/report.rb +163 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/reset.rb +64 -0
- data/lib/studium/curricula/show_lectures_of_this_curriculum_id/show_lectures_of_this_curriculum_id.rb +38 -0
- data/lib/studium/curricula/show_solved_percentage_among_the_registered_curricula.rb +87 -0
- data/lib/studium/ects/boku_ects_splitter.rb +128 -0
- data/lib/studium/ects/ects_per_university.rb +179 -0
- data/lib/studium/ects/ects_scanner.rb +141 -0
- data/lib/studium/ects/ects_to_university_parser.rb +142 -0
- data/lib/studium/ects/last_entry_is_curriculum.rb +150 -0
- data/lib/studium/ects/n_ects_in_these_lectures.rb +196 -0
- data/lib/studium/ects/n_ects_points_in_mandatory_presence_courses.rb +50 -0
- data/lib/studium/ects/return_n_ects_from_this_file.rb +59 -0
- data/lib/studium/ects/return_n_ects_from_this_url.rb +196 -0
- data/lib/studium/ects/search_for_n_ects.rb +614 -0
- data/lib/studium/ects/show_completed_ects_in_all_curricula.rb +191 -0
- data/lib/studium/ects/show_passed_credits_per_curriculum.rb +276 -0
- data/lib/studium/ects/simple_total_ects_points.rb +135 -0
- data/lib/studium/ects/solved_ects/constants.rb +19 -0
- data/lib/studium/ects/solved_ects/reset.rb +51 -0
- data/lib/studium/ects/solved_ects/solved_ects.rb +325 -0
- data/lib/studium/ects/solved_ects_per_university/reset.rb +25 -0
- data/lib/studium/ects/solved_ects_per_university/solved_ects_per_university.rb +106 -0
- data/lib/studium/ects/still_missing.rb +129 -0
- data/lib/studium/ects/sum_of_ects.rb +144 -0
- data/lib/studium/encoding/encoding.rb +108 -0
- data/lib/studium/exam_topics/RNAi_siRNA_and_miRNA +86 -0
- data/lib/studium/exam_topics/abfall_als_ressource +86 -0
- data/lib/studium/exam_topics/advanced_biochemistry +781 -0
- data/lib/studium/exam_topics/advanced_biotechnology +214 -0
- data/lib/studium/exam_topics/advanced_cellbiology +27 -0
- data/lib/studium/exam_topics/advanced_chemistry +504 -0
- data/lib/studium/exam_topics/advanced_microbiology +43 -0
- data/lib/studium/exam_topics/advanced_topics_in_plant_sciences +85 -0
- data/lib/studium/exam_topics/advanced_virology +218 -0
- data/lib/studium/exam_topics/ageing +114 -0
- data/lib/studium/exam_topics/agrar_ecology +63 -0
- data/lib/studium/exam_topics/agrarmarkt +71 -0
- data/lib/studium/exam_topics/agrarphysik +35 -0
- data/lib/studium/exam_topics/alcohols +29 -0
- data/lib/studium/exam_topics/algorithms +52 -0
- data/lib/studium/exam_topics/allergie +75 -0
- data/lib/studium/exam_topics/allgemeine_genetik +1006 -0
- data/lib/studium/exam_topics/allgemeine_mikrobiologie +946 -0
- data/lib/studium/exam_topics/aminoacids +438 -0
- data/lib/studium/exam_topics/analytische_chemie_1 +132 -0
- data/lib/studium/exam_topics/analytische_chemie_2 +31 -0
- data/lib/studium/exam_topics/anatomie +290 -0
- data/lib/studium/exam_topics/anorganische_chemie +311 -0
- data/lib/studium/exam_topics/anthropologie +116 -0
- data/lib/studium/exam_topics/antibodies_and_antigens +764 -0
- data/lib/studium/exam_topics/apoptosis +35 -0
- data/lib/studium/exam_topics/archaea +60 -0
- data/lib/studium/exam_topics/architecture +8 -0
- data/lib/studium/exam_topics/artificial_intelligence +81 -0
- data/lib/studium/exam_topics/atomemissionsspektrometrie +6 -0
- data/lib/studium/exam_topics/audio +11 -0
- data/lib/studium/exam_topics/bacteriophages +240 -0
- data/lib/studium/exam_topics/basic_biochemistry +1002 -0
- data/lib/studium/exam_topics/basic_biotechnology +1001 -0
- data/lib/studium/exam_topics/basic_chemistry +1007 -0
- data/lib/studium/exam_topics/basic_virology +1008 -0
- data/lib/studium/exam_topics/bauwesen +6 -0
- data/lib/studium/exam_topics/betriebssysteme +126 -0
- data/lib/studium/exam_topics/betriebswirtschaftslehre +29 -0
- data/lib/studium/exam_topics/bioanalytik_und_biosensoren +382 -0
- data/lib/studium/exam_topics/biochips +78 -0
- data/lib/studium/exam_topics/bioelektrochemie +57 -0
- data/lib/studium/exam_topics/biofilms +22 -0
- data/lib/studium/exam_topics/bioinformatics +503 -0
- data/lib/studium/exam_topics/biological_therapeutics +153 -0
- data/lib/studium/exam_topics/biologie +137 -0
- data/lib/studium/exam_topics/biomarkers +106 -0
- data/lib/studium/exam_topics/biomaterials +89 -0
- data/lib/studium/exam_topics/biomembranes +6 -0
- data/lib/studium/exam_topics/bionik +65 -0
- data/lib/studium/exam_topics/biophysik +34 -0
- data/lib/studium/exam_topics/biopolymers +10 -0
- data/lib/studium/exam_topics/bioprozesstechnik +149 -0
- data/lib/studium/exam_topics/bioressourcenmanagement +78 -0
- data/lib/studium/exam_topics/bodenkunde +373 -0
- data/lib/studium/exam_topics/bodenmikrobiologie +40 -0
- data/lib/studium/exam_topics/cancerbiology +442 -0
- data/lib/studium/exam_topics/cell_cultures +155 -0
- data/lib/studium/exam_topics/cellbiology +995 -0
- data/lib/studium/exam_topics/cellular_transport_and_protein_secretion +27 -0
- data/lib/studium/exam_topics/cellulose +6 -0
- data/lib/studium/exam_topics/chemische_technologie_anorganischer_stoffe +209 -0
- data/lib/studium/exam_topics/chemische_technologie_organischer_stoffe +25 -0
- data/lib/studium/exam_topics/chemisches_labor +60 -0
- data/lib/studium/exam_topics/chemotaxis_and_motility_in_prokaryotes +87 -0
- data/lib/studium/exam_topics/citric_acid_cycle +80 -0
- data/lib/studium/exam_topics/clinical_microbiology +492 -0
- data/lib/studium/exam_topics/computer_graphics +5 -0
- data/lib/studium/exam_topics/computer_science +280 -0
- data/lib/studium/exam_topics/crispr +28 -0
- data/lib/studium/exam_topics/cyanobacteria +42 -0
- data/lib/studium/exam_topics/cytogenetics_and_chromosome_biology +551 -0
- data/lib/studium/exam_topics/cytokines +5 -0
- data/lib/studium/exam_topics/databases_and_sql +106 -0
- data/lib/studium/exam_topics/dna_mutation_and_dna_repair +35 -0
- data/lib/studium/exam_topics/dna_replication +56 -0
- data/lib/studium/exam_topics/ecogenetics +26 -0
- data/lib/studium/exam_topics/ecological_agriculture +12 -0
- data/lib/studium/exam_topics/ecology +314 -0
- data/lib/studium/exam_topics/economy +211 -0
- data/lib/studium/exam_topics/elektronenmikroskopie +354 -0
- data/lib/studium/exam_topics/elektrophorese +89 -0
- data/lib/studium/exam_topics/elektrotechnik_und_elektrizit/303/244t +41 -0
- data/lib/studium/exam_topics/elisa +54 -0
- data/lib/studium/exam_topics/embryologie_und_entwicklung +547 -0
- data/lib/studium/exam_topics/endospores_and_spores +104 -0
- data/lib/studium/exam_topics/enzymes_and_cofactors +345 -0
- data/lib/studium/exam_topics/epigenetik +179 -0
- data/lib/studium/exam_topics/ethik +138 -0
- data/lib/studium/exam_topics/evolution_and_evolutionary_genetics +328 -0
- data/lib/studium/exam_topics/excel +7 -0
- data/lib/studium/exam_topics/fish +19 -0
- data/lib/studium/exam_topics/fluorescence_microscopy +7 -0
- data/lib/studium/exam_topics/food_microbiology_and_food_biotechnology +71 -0
- data/lib/studium/exam_topics/forensik +11 -0
- data/lib/studium/exam_topics/forstwirtschaft +53 -0
- data/lib/studium/exam_topics/fortgeschrittene_genetik +511 -0
- data/lib/studium/exam_topics/fortgeschrittene_gentechnik +211 -0
- data/lib/studium/exam_topics/fortgeschrittene_physik +6 -0
- data/lib/studium/exam_topics/fungi +79 -0
- data/lib/studium/exam_topics/genetische_krankheiten +176 -0
- data/lib/studium/exam_topics/genexpression +1008 -0
- data/lib/studium/exam_topics/genomics_and_metagenomics +244 -0
- data/lib/studium/exam_topics/gentechnik_und_praktische_biochemie +901 -0
- data/lib/studium/exam_topics/geochemistry +67 -0
- data/lib/studium/exam_topics/geography +8 -0
- data/lib/studium/exam_topics/geologie_und_mineralogie +621 -0
- data/lib/studium/exam_topics/geometrie +47 -0
- data/lib/studium/exam_topics/geschichte +93 -0
- data/lib/studium/exam_topics/gluconeogenesis +59 -0
- data/lib/studium/exam_topics/glycogen +25 -0
- data/lib/studium/exam_topics/glycolysis +109 -0
- data/lib/studium/exam_topics/glykomik +100 -0
- data/lib/studium/exam_topics/glyoxylatzyklus +31 -0
- data/lib/studium/exam_topics/grassland_cultivation +32 -0
- data/lib/studium/exam_topics/hormone +134 -0
- data/lib/studium/exam_topics/html +7 -0
- data/lib/studium/exam_topics/human_ecology +8 -0
- data/lib/studium/exam_topics/hygiene +191 -0
- data/lib/studium/exam_topics/imaging_and_microscopy +241 -0
- data/lib/studium/exam_topics/immunanalytik +94 -0
- data/lib/studium/exam_topics/immunologie +982 -0
- data/lib/studium/exam_topics/informatik +97 -0
- data/lib/studium/exam_topics/innate_immunity +22 -0
- data/lib/studium/exam_topics/insekten +57 -0
- data/lib/studium/exam_topics/insulin_and_diabetes +57 -0
- data/lib/studium/exam_topics/java +502 -0
- data/lib/studium/exam_topics/javascript +12 -0
- data/lib/studium/exam_topics/klima +6 -0
- data/lib/studium/exam_topics/kryptographie +5 -0
- data/lib/studium/exam_topics/landtechnik +26 -0
- data/lib/studium/exam_topics/lebensmittel +208 -0
- data/lib/studium/exam_topics/lebensmitteltechnologie +16 -0
- data/lib/studium/exam_topics/linux +5 -0
- data/lib/studium/exam_topics/lipids +94 -0
- data/lib/studium/exam_topics/macroeconomics +40 -0
- data/lib/studium/exam_topics/mathematics +254 -0
- data/lib/studium/exam_topics/medizin_und_biomedizinische_technik +250 -0
- data/lib/studium/exam_topics/medizinische_chemie_und_pharmazie +398 -0
- data/lib/studium/exam_topics/messtechnik_und_regeltechnik +104 -0
- data/lib/studium/exam_topics/metabolismus +406 -0
- data/lib/studium/exam_topics/microbial_ecology +35 -0
- data/lib/studium/exam_topics/microcontrollers +11 -0
- data/lib/studium/exam_topics/mikrobielle_lebensgemeinschaften +33 -0
- data/lib/studium/exam_topics/mikrobielle_physiologie +172 -0
- data/lib/studium/exam_topics/mitochondria +32 -0
- data/lib/studium/exam_topics/mixed +278 -0
- data/lib/studium/exam_topics/molecular_biology_of_plants +242 -0
- data/lib/studium/exam_topics/molekulare_medizin +131 -0
- data/lib/studium/exam_topics/nanotechnologie +453 -0
- data/lib/studium/exam_topics/nature_conservation_and_biodiversity +166 -0
- data/lib/studium/exam_topics/naturstoffe +9 -0
- data/lib/studium/exam_topics/netzwerke +32 -0
- data/lib/studium/exam_topics/neurobiology +267 -0
- data/lib/studium/exam_topics/nucleotide_sequencing +32 -0
- data/lib/studium/exam_topics/nutztierethologie +11 -0
- data/lib/studium/exam_topics/object_oriented_modeling +14 -0
- data/lib/studium/exam_topics/obstbau +234 -0
- data/lib/studium/exam_topics/organische_chemie +1007 -0
- data/lib/studium/exam_topics/organische_chemie_2 +118 -0
- data/lib/studium/exam_topics/paleobiology +35 -0
- data/lib/studium/exam_topics/parasitic_diseases_and_molecular_infection_biology +335 -0
- data/lib/studium/exam_topics/patent_law +55 -0
- data/lib/studium/exam_topics/pathologie +717 -0
- data/lib/studium/exam_topics/pcr +144 -0
- data/lib/studium/exam_topics/pentosephosphatweg +41 -0
- data/lib/studium/exam_topics/peroxisomes_glycosomes_and_lysosomes +54 -0
- data/lib/studium/exam_topics/pflanzenanatomie +255 -0
- data/lib/studium/exam_topics/pflanzenbau +24 -0
- data/lib/studium/exam_topics/pflanzenschutz +35 -0
- data/lib/studium/exam_topics/pflanzenwissenschaften +1009 -0
- data/lib/studium/exam_topics/pharmaceutical_biotechnology +250 -0
- data/lib/studium/exam_topics/physik +433 -1
- data/lib/studium/exam_topics/physikalische_chemie +86 -0
- data/lib/studium/exam_topics/physiology_and_histology +506 -0
- data/lib/studium/exam_topics/phytochemie +33 -0
- data/lib/studium/exam_topics/plant_biotechnology +128 -0
- data/lib/studium/exam_topics/plant_breeding +64 -0
- data/lib/studium/exam_topics/plant_development +50 -0
- data/lib/studium/exam_topics/populationsgenetik +136 -0
- data/lib/studium/exam_topics/posttranslationale_modifikation_von_proteinen +191 -0
- data/lib/studium/exam_topics/projektmanagement +219 -0
- data/lib/studium/exam_topics/prokaryote_genetics +531 -0
- data/lib/studium/exam_topics/protein_engineering +8 -0
- data/lib/studium/exam_topics/proteolyse +33 -0
- data/lib/studium/exam_topics/proteomik +40 -0
- data/lib/studium/exam_topics/prozesstechnik +95 -0
- data/lib/studium/exam_topics/psychologie +13 -0
- data/lib/studium/exam_topics/python +353 -0
- data/lib/studium/exam_topics/quality_management +256 -0
- data/lib/studium/exam_topics/rechtsgrundlagen +115 -0
- data/lib/studium/exam_topics/research_topics_in_immunobiology +42 -0
- data/lib/studium/exam_topics/rna_and_dna +395 -0
- data/lib/studium/exam_topics/rna_seq +11 -0
- data/lib/studium/exam_topics/ruby +146 -0
- data/lib/studium/exam_topics/ruby_on_rails +63 -0
- data/lib/studium/exam_topics/scientific_writing_and_publishing +38 -0
- data/lib/studium/exam_topics/semisynthese_von_proteinen_und_nukleotiden +120 -0
- data/lib/studium/exam_topics/sexualbiologie +62 -0
- data/lib/studium/exam_topics/signal_transduction_and_laser_systems +167 -0
- data/lib/studium/exam_topics/splicing_exons_and_introns +63 -0
- data/lib/studium/exam_topics/statistik +233 -0
- data/lib/studium/exam_topics/stemcells +158 -0
- data/lib/studium/exam_topics/stickstofffixierung +75 -0
- data/lib/studium/exam_topics/structural_bioinformatics +54 -0
- data/lib/studium/exam_topics/strukturbiologie +380 -0
- data/lib/studium/exam_topics/system_biology_and_synthetic_biology +101 -0
- data/lib/studium/exam_topics/systematische_zoologie +433 -0
- data/lib/studium/exam_topics/technical_ecology +144 -0
- data/lib/studium/exam_topics/technische_chemie +202 -0
- data/lib/studium/exam_topics/technische_grundlagen_der_informatik +26 -0
- data/lib/studium/exam_topics/technische_mikrobiologie +393 -0
- data/lib/studium/exam_topics/technisches_zeichnen +5 -0
- data/lib/studium/exam_topics/the_bacterial_cell_wall +97 -0
- data/lib/studium/exam_topics/the_c_plus_plus_programming_language +489 -0
- data/lib/studium/exam_topics/the_c_programming_language +129 -0
- data/lib/studium/exam_topics/the_cellcycle +81 -0
- data/lib/studium/exam_topics/the_european_union +119 -0
- data/lib/studium/exam_topics/the_interferon_system +38 -0
- data/lib/studium/exam_topics/the_microbiome +163 -0
- data/lib/studium/exam_topics/the_universe +12 -0
- data/lib/studium/exam_topics/theoretische_chemie +5 -0
- data/lib/studium/exam_topics/theoretische_informatik +157 -0
- data/lib/studium/exam_topics/tierzucht +94 -0
- data/lib/studium/exam_topics/toxikologie +408 -0
- data/lib/studium/exam_topics/transcription +82 -0
- data/lib/studium/exam_topics/translation_ribosomes_and_translational_control +142 -0
- data/lib/studium/exam_topics/umweltbiotechnologie +63 -0
- data/lib/studium/exam_topics/umweltchemie +233 -0
- data/lib/studium/exam_topics/urbanism_and_traffic +19 -0
- data/lib/studium/exam_topics/urea_cycle +55 -0
- data/lib/studium/exam_topics/vaccines_and_vaccination +242 -0
- data/lib/studium/exam_topics/vectors_and_gene_therapy +240 -0
- data/lib/studium/exam_topics/verfahrenstechnik +32 -0
- data/lib/studium/exam_topics/veterinary_medicine +10 -0
- data/lib/studium/exam_topics/vitamine +24 -0
- data/lib/studium/exam_topics/wasserkunde +137 -0
- data/lib/studium/exam_topics/weinbau +59 -0
- data/lib/studium/exam_topics/wissenschaft +18 -0
- data/lib/studium/exam_topics/yeast +102 -0
- data/lib/studium/exam_topics/zoologie +330 -0
- data/lib/studium/exams/afterburn/afterburn.rb +257 -0
- data/lib/studium/exams/ask_exam_from_the_upcoming_exams_pool.rb +150 -0
- data/lib/studium/exams/ask_exam_topic_question.rb +112 -0
- data/lib/studium/exams/ask_question_from_alias.rb +141 -0
- data/lib/studium/exams/ask_question_from_any_of_the_still_missing_lectures.rb +131 -0
- data/lib/studium/exams/ask_question_from_grouped_themes.rb +141 -0
- data/lib/studium/exams/ask_question_from_last_topic.rb +91 -0
- data/lib/studium/exams/ask_random_question.rb +195 -0
- data/lib/studium/exams/autoinclude.rb +7 -0
- data/lib/studium/exams/csv/create_csv_passed_exams_file.rb +217 -0
- data/lib/studium/exams/cycle.rb +291 -0
- data/lib/studium/exams/dataset.rb +123 -0
- data/lib/studium/exams/designate_ten_random_exam_topics/designate_ten_random_exam_topics.rb +88 -0
- data/lib/studium/exams/exam/exam.rb +130 -0
- data/lib/studium/exams/exam_question/README.md +3 -0
- data/lib/studium/exams/exam_question/answer.rb +177 -0
- data/lib/studium/exams/exam_question/constants.rb +111 -0
- data/lib/studium/exams/exam_question/exam_question.rb +1135 -0
- data/lib/studium/exams/exam_question/menu.rb +333 -0
- data/lib/studium/exams/exam_question/misc.rb +895 -0
- data/lib/studium/exams/exam_question/question.rb +91 -0
- data/lib/studium/exams/exam_question/reset.rb +96 -0
- data/lib/studium/exams/exam_registration_at/constants.rb +49 -0
- data/lib/studium/exams/exam_registration_at/exam_registration_at.rb +242 -0
- data/lib/studium/exams/exam_registration_at/help.rb +46 -0
- data/lib/studium/exams/exam_registration_at/menu.rb +81 -0
- data/lib/studium/exams/exam_registration_at/report_and_show.rb +133 -0
- data/lib/studium/exams/exam_registration_at/reset.rb +54 -0
- data/lib/studium/exams/exam_statistics_from_this_file/exam_statistics_from_this_file.rb +119 -0
- data/lib/studium/exams/exam_topics.rb +194 -0
- data/lib/studium/exams/exams.rb +20 -0
- data/lib/studium/exams/exams_per_month/exams_per_month.rb +2438 -0
- data/lib/studium/exams/exams_this_week.rb +182 -0
- data/lib/studium/exams/fix_exam_dates.rb +121 -0
- data/lib/studium/exams/frozen.rb +36 -0
- data/lib/studium/exams/last_exams/last_exams.rb +398 -0
- data/lib/studium/exams/lectures_without_exam_entry.rb +137 -0
- data/lib/studium/exams/mandatory_continuous_assessment/mandatory_continuous_assessment.rb +1956 -0
- data/lib/studium/exams/move_the_last_exam_question_to_the_top_of_the_file/move_the_last_exam_question_to_the_top_of_the_file.rb +111 -0
- data/lib/studium/exams/n_exams_in_these_topics.rb +404 -0
- data/lib/studium/exams/next_exam.rb +107 -0
- data/lib/studium/exams/next_exams.rb +378 -0
- data/lib/studium/exams/open_exam_associated_url.rb +154 -0
- data/lib/studium/exams/open_last_exam_question_asked_file/constants.rb +15 -0
- data/lib/studium/exams/open_last_exam_question_asked_file/initialize.rb +29 -0
- data/lib/studium/exams/open_last_exam_question_asked_file/open_last_exam_question_asked_file.rb +109 -0
- data/lib/studium/exams/pr/303/274fung.rb +289 -0
- data/lib/studium/exams/push_solved_questions_on_top.rb +180 -0
- data/lib/studium/exams/questions_solved_from_day_to_day/questions_solved_from_day_to_day.rb +377 -0
- data/lib/studium/exams/remote_ftp_url.rb +52 -0
- data/lib/studium/exams/repeat_last_question.rb +78 -0
- data/lib/studium/exams/show_all_passed_exams_of_this_university.rb +252 -0
- data/lib/studium/exams/show_backlog_of_exams.rb +117 -0
- data/lib/studium/exams/show_next_exams_for.rb +133 -0
- data/lib/studium/exams/show_themes/constants.rb +28 -0
- data/lib/studium/exams/show_themes/menu.rb +61 -0
- data/lib/studium/exams/show_themes/misc.rb +537 -0
- data/lib/studium/exams/show_themes/reset.rb +62 -0
- data/lib/studium/exams/show_themes/show_themes.rb +27 -0
- data/lib/studium/exams/show_upcoming_exams/consider_autogenerating_exam_aliases.rb +181 -0
- data/lib/studium/exams/show_upcoming_exams/constants.rb +82 -0
- data/lib/studium/exams/show_upcoming_exams/help.rb +33 -0
- data/lib/studium/exams/show_upcoming_exams/initialize.rb +77 -0
- data/lib/studium/exams/show_upcoming_exams/menu.rb +60 -0
- data/lib/studium/exams/show_upcoming_exams/report.rb +200 -0
- data/lib/studium/exams/show_upcoming_exams/reset.rb +45 -0
- data/lib/studium/exams/show_upcoming_exams/run.rb +20 -0
- data/lib/studium/exams/show_upcoming_exams/show_upcoming_exams.rb +544 -0
- data/lib/studium/exams/solve_all_questions_from_this_topic.rb +114 -0
- data/lib/studium/exams/solved/constants.rb +32 -0
- data/lib/studium/exams/solved/help.rb +24 -0
- data/lib/studium/exams/solved/initialize.rb +55 -0
- data/lib/studium/exams/solved/menu.rb +41 -0
- data/lib/studium/exams/solved/reset.rb +28 -0
- data/lib/studium/exams/solved/solved.rb +313 -0
- data/lib/studium/exams/unsolve_all_questions_from_this_topic.rb +162 -0
- data/lib/studium/exams/upcoming_exams/constants.rb +15 -0
- data/lib/studium/exams/upcoming_exams/help.rb +41 -0
- data/lib/studium/exams/upcoming_exams/initialize.rb +27 -0
- data/lib/studium/exams/upcoming_exams/menu.rb +79 -0
- data/lib/studium/exams/upcoming_exams/misc.rb +415 -0
- data/lib/studium/exams/upcoming_exams/reset.rb +34 -0
- data/lib/studium/exams/upcoming_exams/run.rb +26 -0
- data/lib/studium/exams/upcoming_exams/upcoming_exams.rb +32 -0
- data/lib/studium/exams/upcoming_exams_at_the_boku/constants.rb +23 -0
- data/lib/studium/exams/upcoming_exams_at_the_boku/html.rb +64 -0
- data/lib/studium/exams/upcoming_exams_at_the_boku/upcoming_exams_at_the_boku.rb +194 -0
- data/lib/studium/exams/upcoming_exams_dataset.rb +247 -0
- data/lib/studium/exams/upload_exam_topics.rb +360 -0
- data/lib/studium/graphviz/README.md +4 -0
- data/lib/studium/graphviz/bachelor_vector_based_strategies.dot +160 -0
- data/lib/studium/graphviz/master_vector_based_strategies.dot +46 -0
- data/lib/studium/gui/gtk3/README.md +1 -0
- data/lib/studium/gui/gtk3/ask_exam_question/ask_exam_question.config +6 -0
- data/lib/studium/gui/gtk3/ask_exam_question/ask_exam_question.rb +760 -0
- data/lib/studium/gui/gtk3/ask_exam_question/manifest.yml +12 -0
- data/lib/studium/gui/gtk3/control_panel/control_panel.rb +39 -0
- data/lib/studium/gui/gtk3/curriculum_viewer/curriculum_viewer.rb +510 -0
- data/lib/studium/gui/gtk3/ects_per_university/ects_per_university.rb +217 -0
- data/lib/studium/gui/gtk3/exam_question_widget/exam_question_widget.rb +1887 -0
- data/lib/studium/gui/gtk3/expand_time_range/expand_time_range.rb +34 -0
- data/lib/studium/gui/gtk3/information_about_a_lecture/information_about_a_lecture.rb +34 -0
- data/lib/studium/gui/gtk3/lecture_information/lecture_information.rb +200 -0
- data/lib/studium/gui/gtk3/show_upcoming_exams/show_upcoming_exams.rb +34 -0
- data/lib/studium/gui/java/exam_question/ExamQuestion$1.class +0 -0
- data/lib/studium/gui/java/exam_question/ExamQuestion.class +0 -0
- data/lib/studium/gui/java/exam_question/ExamQuestion.java +215 -0
- data/lib/studium/gui/javafx/exam_question_widget/exam_question_widget.rb +58 -0
- data/lib/studium/gui/jruby/exam_question_widget/exam_question_widget.rb +317 -0
- data/lib/studium/gui/libui/ask_exam_question/ask_exam_question.rb +349 -0
- data/lib/studium/gui/shared_code/control_panel/control_panel_module.rb +314 -0
- data/lib/studium/gui/shared_code/exam_question_widget/exam_question_widget_module.rb +39 -0
- data/lib/studium/gui/shared_code/expand_time_range/expand_time_range.css +0 -0
- data/lib/studium/gui/shared_code/expand_time_range/expand_time_range_module.rb +190 -0
- data/lib/studium/gui/shared_code/information_about_a_lecture/information_about_a_lecture_module.rb +180 -0
- data/lib/studium/gui/shared_code/show_upcoming_exams/show_upcoming_exams_module.rb +206 -0
- data/lib/studium/images/libui_ask_exam_question.png +0 -0
- data/lib/studium/images/small_logos/DNA.png +0 -0
- data/lib/studium/images/small_logos/README.md +2 -0
- data/lib/studium/images/studies_favicon.png +0 -0
- data/lib/studium/java/Mkdir.java +15 -0
- data/lib/studium/java/README.md +2 -0
- data/lib/studium/java/ask_exam_question/AskExamQuestion.java +477 -0
- data/lib/studium/java/solved/Solved.class +0 -0
- data/lib/studium/java/solved/Solved.java +110 -0
- data/lib/studium/java/utility_scripts/OpenLastExamQuestionurlLinkViaTheBrowser.class +0 -0
- data/lib/studium/java/utility_scripts/OpenLastExamQuestionurlLinkViaTheBrowser.java +80 -0
- data/lib/studium/logging/README.md +2 -0
- data/lib/studium/logging/ensure_that_the_log_directory_exists.rb +47 -0
- data/lib/studium/logging/html_log_directory.rb +41 -0
- data/lib/studium/logging/log_directory.rb +112 -0
- data/lib/studium/logging/store_last_question_asked_into_file.rb +137 -0
- data/lib/studium/parsers/README.md +2 -0
- data/lib/studium/parsers/custom_exam_results_parser.rb +206 -0
- data/lib/studium/parsers/parse_lva_dates.rb +190 -0
- data/lib/studium/parsers/parse_remote_lecture.rb +325 -0
- data/lib/studium/project/project.rb +76 -0
- data/lib/studium/requires/common_popular_requires.rb +37 -0
- data/lib/studium/requires/commonly_used_requires.rb +14 -0
- data/lib/studium/requires/require_class_exams_solved.rb +7 -0
- data/lib/studium/requires/require_ects_scripts.rb +27 -0
- data/lib/studium/requires/require_encoding.rb +7 -0
- data/lib/studium/requires/require_the_check_and_sanitize_files.rb +31 -0
- data/lib/studium/requires/require_the_curricula_files.rb +28 -0
- data/lib/studium/requires/require_the_exam_question_class.rb +7 -0
- data/lib/studium/requires/require_the_exams_files.rb +45 -0
- data/lib/studium/requires/require_the_logging_files.rb +23 -0
- data/lib/studium/requires/require_the_parsers.rb +28 -0
- data/lib/studium/requires/require_the_studium_constants.rb +10 -0
- data/lib/studium/requires/require_the_studium_project.rb +54 -0
- data/lib/studium/requires/require_the_toplevel_methods.rb +27 -0
- data/lib/studium/requires/require_the_utility_scripts.rb +49 -0
- data/lib/studium/requires/require_upcoming_exams.rb +7 -0
- data/lib/studium/requires/require_yaml.rb +7 -0
- data/lib/studium/requires/return_remote_homepage_of_this_lecture.rb +7 -0
- data/lib/studium/requires/with_GUI.rb +13 -0
- data/lib/studium/requires/www_mode.rb +17 -0
- data/lib/studium/statistics/README.md +4 -0
- data/lib/studium/statistics/best_exam_months.rb +92 -0
- data/lib/studium/statistics/curriculum_comparer.rb +336 -0
- data/lib/studium/statistics/determine_exam_statistics_from_this_file.rb +142 -0
- data/lib/studium/statistics/exam_topics_that_are_about_to_be_completed.rb +119 -0
- data/lib/studium/statistics/max_stats.rb +170 -0
- data/lib/studium/statistics/new_questions_per_year.rb +147 -0
- data/lib/studium/statistics/report_how_many_ects_points_per_curriculum_were_completed.rb +167 -0
- data/lib/studium/statistics/report_how_many_exam_questions_were_answered.rb +473 -0
- data/lib/studium/statistics/show_exam_statistics.rb +60 -0
- data/lib/studium/statistics/show_which_courses_are_in_a_bachelor_or_master_curriculum_respectively.rb +104 -0
- data/lib/studium/statistics/top_stats.rb +127 -0
- data/lib/studium/toplevel_methods/all_passed_exams.rb +37 -0
- data/lib/studium/toplevel_methods/already_solved_this_lecture.rb +100 -0
- data/lib/studium/toplevel_methods/available_topics.rb +156 -0
- data/lib/studium/toplevel_methods/average_grade.rb +141 -0
- data/lib/studium/toplevel_methods/calculate_pr/303/274fungsimmanente_lectures_from_this_file.rb +55 -0
- data/lib/studium/toplevel_methods/copy_the_last_backup_of_file_lecture_information.rb +34 -0
- data/lib/studium/toplevel_methods/curriculum_related_code.rb +999 -0
- data/lib/studium/toplevel_methods/determine_local_directory_of_this_lecture.rb +72 -0
- data/lib/studium/toplevel_methods/does_this_course_require_mandatory_presence.rb +51 -0
- data/lib/studium/toplevel_methods/download.rb +163 -0
- data/lib/studium/toplevel_methods/e.rb +16 -0
- data/lib/studium/toplevel_methods/ects_from_lectures.rb +250 -0
- data/lib/studium/toplevel_methods/editor.rb +65 -0
- data/lib/studium/toplevel_methods/esystem.rb +22 -0
- data/lib/studium/toplevel_methods/filter_away_invalid_questions.rb +77 -0
- data/lib/studium/toplevel_methods/find_exam_topic_and_exam_title.rb +3442 -0
- data/lib/studium/toplevel_methods/handle_archive_of_the_exam_questions.rb +136 -0
- data/lib/studium/toplevel_methods/has_this_lecture_been_already_passed_but_the_id_was_changed_lateron.rb +42 -0
- data/lib/studium/toplevel_methods/has_this_module_been_completed.rb +206 -0
- data/lib/studium/toplevel_methods/install_the_project_on_the_given_hostsystem.rb +32 -0
- data/lib/studium/toplevel_methods/is_on_roebe.rb +26 -0
- data/lib/studium/toplevel_methods/is_this_exam_topic_included.rb +46 -0
- data/lib/studium/toplevel_methods/is_this_homepage_registered.rb +31 -0
- data/lib/studium/toplevel_methods/is_this_lecture_a_practical_course.rb +100 -0
- data/lib/studium/toplevel_methods/is_this_lecture_registered_in_upcoming_exams.rb +42 -0
- data/lib/studium/toplevel_methods/java.rb +32 -0
- data/lib/studium/toplevel_methods/lecture_information.rb +106 -0
- data/lib/studium/toplevel_methods/lva_numbers.rb +355 -0
- data/lib/studium/toplevel_methods/main_dataset.rb +73 -0
- data/lib/studium/toplevel_methods/methods_related_to_directories.rb +225 -0
- data/lib/studium/toplevel_methods/methods_related_to_files.rb +205 -0
- data/lib/studium/toplevel_methods/misc.rb +169 -0
- data/lib/studium/toplevel_methods/n_questions_available.rb +137 -0
- data/lib/studium/toplevel_methods/n_topics_available.rb +63 -0
- data/lib/studium/toplevel_methods/names_of_all_solved_exams.rb +71 -0
- data/lib/studium/toplevel_methods/note_down_the_start_time_and_how_many_exams_have_been_already_solved.rb +69 -0
- data/lib/studium/toplevel_methods/opnn.rb +25 -0
- data/lib/studium/toplevel_methods/passed_this_exam_on.rb +105 -0
- data/lib/studium/toplevel_methods/pristine.rb +69 -0
- data/lib/studium/toplevel_methods/read_delay_between_questions_from_file.rb +34 -0
- data/lib/studium/toplevel_methods/regexes.rb +90 -0
- data/lib/studium/toplevel_methods/registered_for_this_exam.rb +62 -0
- data/lib/studium/toplevel_methods/remove_comments.rb +26 -0
- data/lib/studium/toplevel_methods/remove_exam_topics_that_were_already_answered.rb +27 -0
- data/lib/studium/toplevel_methods/remove_tags.rb +32 -0
- data/lib/studium/toplevel_methods/report.rb +419 -0
- data/lib/studium/toplevel_methods/return_all_exams_on_this_day.rb +66 -0
- data/lib/studium/toplevel_methods/return_dataset_for_this_exam_topic.rb +41 -0
- data/lib/studium/toplevel_methods/return_div_timetable_of_upcoming_exams.rb +498 -0
- data/lib/studium/toplevel_methods/return_ects_from_this_lecture_stored_in_the_file_lecture_information.rb +194 -0
- data/lib/studium/toplevel_methods/return_hash_of_already_solved_lectures.rb +46 -0
- data/lib/studium/toplevel_methods/return_last_exam_question.rb +34 -0
- data/lib/studium/toplevel_methods/return_local_path_of_this_pwdstud.rb +60 -0
- data/lib/studium/toplevel_methods/return_lva_number_of_this_lecture.rb +72 -0
- data/lib/studium/toplevel_methods/return_n_percent_solved_from_this_topic.rb +90 -0
- data/lib/studium/toplevel_methods/return_n_questions_were_answered_for_this_topic.rb +60 -0
- data/lib/studium/toplevel_methods/return_proper_university_image.rb +86 -0
- data/lib/studium/toplevel_methods/return_question_answer_string_from_this_topic.rb +63 -0
- data/lib/studium/toplevel_methods/return_remote_homepage_of_this_lecture.rb +9400 -0
- data/lib/studium/toplevel_methods/return_remote_moodle_link_of_this_lecture.rb +1661 -0
- data/lib/studium/toplevel_methods/return_sanitized_dataset_from_the_file_lecture_information.rb +110 -0
- data/lib/studium/toplevel_methods/return_theme_of_the_next_upcoming_exam.rb +38 -0
- data/lib/studium/toplevel_methods/rinstall2.rb +34 -0
- data/lib/studium/toplevel_methods/rti_conflict.rb +35 -0
- data/lib/studium/toplevel_methods/runmode.rb +87 -0
- data/lib/studium/toplevel_methods/sanitized_dataset_from_file_passed_exams_per_month.rb +52 -0
- data/lib/studium/toplevel_methods/set_last_file_for_exam_questions.rb +64 -0
- data/lib/studium/toplevel_methods/set_this_cd_alias_to.rb +86 -0
- data/lib/studium/toplevel_methods/show_passed_exams_having_this_grade.rb +34 -0
- data/lib/studium/toplevel_methods/spacer.rb +18 -0
- data/lib/studium/toplevel_methods/time.rb +239 -0
- data/lib/studium/toplevel_methods/total_ects_points_passed.rb +72 -0
- data/lib/studium/toplevel_methods/try_to_guess_the_most_likely_lva_id.rb +57 -0
- data/lib/studium/toplevel_methods/try_to_return_the_expanded_name_of_this_lecture.rb +63 -0
- data/lib/studium/toplevel_methods/unfinished.rb +51 -0
- data/lib/studium/toplevel_methods/url.rb +100 -0
- data/lib/studium/toplevel_methods/verbose_truth.rb +36 -0
- data/lib/studium/toplevel_methods/when_was_this_lecture_passed.rb +54 -0
- data/lib/studium/toplevel_methods/word_wrap.rb +56 -0
- data/lib/studium/toplevel_methods/write_into_file_related_functionality.rb +189 -0
- data/lib/studium/toplevel_methods/yes_or_no_ja_oder_nein.rb +33 -0
- data/lib/studium/universities_in_austria/README.md +2 -0
- data/lib/studium/universities_in_austria/boku/README.md +4 -0
- data/lib/studium/universities_in_austria/boku/boku_/303/266ffnungszeiten.rb +28 -0
- data/lib/studium/universities_in_austria/boku/show_three_pillars_of_these_lectures.rb +110 -0
- data/lib/studium/universities_in_austria/boku/three_pillars.rb +237 -0
- data/lib/studium/universities_in_austria/tu_vienna/README.md +6 -0
- data/lib/studium/universities_in_austria/tu_vienna/tu_ferien.rb +42 -0
- data/lib/studium/universities_in_austria/tu_vienna/tu_/303/266ffnungszeiten.rb +34 -0
- data/lib/studium/utility_scripts/attribute_lecture_to_curriculum/attribute_boku_lecture_to_curriculum.rb +384 -0
- data/lib/studium/utility_scripts/attribute_lecture_to_curriculum/attribute_lecture_to_curriculum.rb +238 -0
- data/lib/studium/utility_scripts/attribute_lectures_to_university/attribute_lectures_to_university.rb +375 -0
- data/lib/studium/utility_scripts/audio_stats.rb +171 -0
- data/lib/studium/utility_scripts/auto_stud/auto_stud.rb +252 -0
- data/lib/studium/utility_scripts/auto_stud/constants.rb +18 -0
- data/lib/studium/utility_scripts/auto_stud/initialize.rb +23 -0
- data/lib/studium/utility_scripts/auto_stud/misc.rb +18 -0
- data/lib/studium/utility_scripts/autopurge_this_lecture_date.rb +93 -0
- data/lib/studium/utility_scripts/average_grade_of_this_curriculum.rb +101 -0
- data/lib/studium/utility_scripts/calendar/README.md +2 -0
- data/lib/studium/utility_scripts/calendar/calendar.rb +251 -0
- data/lib/studium/utility_scripts/calendar/misc.rb +35 -0
- data/lib/studium/utility_scripts/check_description_of_these_lectures.rb +221 -0
- data/lib/studium/utility_scripts/create_database/create_database.rb +106 -0
- data/lib/studium/utility_scripts/current_lectures_belonging_to_both_bachelor_and_master_curriculum.rb +113 -0
- data/lib/studium/utility_scripts/currently_participating_in_these_lectures/currently_participating_in_these_lectures.rb +104 -0
- data/lib/studium/utility_scripts/display_lecture_url.rb +160 -0
- data/lib/studium/utility_scripts/expand_time_range/expand_time_range.rb +414 -0
- data/lib/studium/utility_scripts/finished_exams_at_this_university.rb +94 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/constants.rb +23 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/foreign_language_percentage.rb +149 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/help.rb +31 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/initialize.rb +25 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/menu.rb +158 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/report.rb +62 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/reset.rb +50 -0
- data/lib/studium/utility_scripts/foreign_language_percentage/run.rb +19 -0
- data/lib/studium/utility_scripts/generate_spreadsheet/generate_spreadsheet.rb +354 -0
- data/lib/studium/utility_scripts/generate_spreadsheet/misc.rb +144 -0
- data/lib/studium/utility_scripts/holidays/holidays.rb +150 -0
- data/lib/studium/utility_scripts/homepage_of_these_courses.rb +118 -0
- data/lib/studium/utility_scripts/lecture_downloader.rb +107 -0
- data/lib/studium/utility_scripts/lectures_attributed_to_universities.rb +336 -0
- data/lib/studium/utility_scripts/lva_dates_of_the_important_courses.rb +111 -0
- data/lib/studium/utility_scripts/lva_nummer.rb +431 -0
- data/lib/studium/utility_scripts/mandatory_lectures_in_this_month/mandatory_lectures_in_this_month.rb +316 -0
- data/lib/studium/utility_scripts/name_of_this_lva_id.rb +110 -0
- data/lib/studium/utility_scripts/new_stud.rb +324 -0
- data/lib/studium/utility_scripts/next_week.rb +103 -0
- data/lib/studium/utility_scripts/open_last_exam_question_url_link_via_the_browser.rb +76 -0
- data/lib/studium/utility_scripts/passed_ects_per_year/passed_ects_per_year.rb +177 -0
- data/lib/studium/utility_scripts/passed_pr/303/274fungsimmanente_courses/passed_pr/303/274fungsimmanente_courses.rb +181 -0
- data/lib/studium/utility_scripts/pdf/README.md +2 -0
- data/lib/studium/utility_scripts/pdf/create_pdf_file_for_this_exam_topic.rb +355 -0
- data/lib/studium/utility_scripts/pdf/hexapdf_support.rb +50 -0
- data/lib/studium/utility_scripts/preparatory_meetings/preparatory_meetings.rb +312 -0
- data/lib/studium/utility_scripts/priority.rb +164 -0
- data/lib/studium/utility_scripts/priority_points/priority_points.rb +263 -0
- data/lib/studium/utility_scripts/publish_my_exams.rb +174 -0
- data/lib/studium/utility_scripts/regexes/README.md +1 -0
- data/lib/studium/utility_scripts/regexes/generate_regex.rb +300 -0
- data/lib/studium/utility_scripts/regexes/generate_regexes_for_the_available_moodle_links.rb +55 -0
- data/lib/studium/utility_scripts/regexes/generate_regexes_for_the_registered_lectures.rb +48 -0
- data/lib/studium/utility_scripts/report_outdated_timetable_entries/report_outdated_timetable_entries.rb +142 -0
- data/lib/studium/utility_scripts/report_total_amount_of_questions_and_answers_for.rb +116 -0
- data/lib/studium/utility_scripts/report_whether_this_lecture_is_registered_in_the_file_lecture_information.rb +128 -0
- data/lib/studium/utility_scripts/resolve_practical_courses_date_conflicts/individual_resolve_practical_courses_date_conflicts.rb +254 -0
- data/lib/studium/utility_scripts/resolve_practical_courses_date_conflicts/resolve_practical_courses_date_conflicts.rb +265 -0
- data/lib/studium/utility_scripts/scrape_remote_university_url.rb +138 -0
- data/lib/studium/utility_scripts/semester_schedule_creator/semester_container.rb +144 -0
- data/lib/studium/utility_scripts/semester_schedule_creator/semester_schedule_creator.rb +374 -0
- data/lib/studium/utility_scripts/semesterplaner.rb +289 -0
- data/lib/studium/utility_scripts/set_aliases_based_on_this_file.rb +95 -0
- data/lib/studium/utility_scripts/show_all_passed_master_lectures.rb +119 -0
- data/lib/studium/utility_scripts/show_conflicting_lva_lectures/show_conflicting_lva_lectures.rb +1238 -0
- data/lib/studium/utility_scripts/show_descriptions_of_lectures_belonging_to_this_module/constants.rb +23 -0
- data/lib/studium/utility_scripts/show_descriptions_of_lectures_belonging_to_this_module/menu.rb +63 -0
- data/lib/studium/utility_scripts/show_descriptions_of_lectures_belonging_to_this_module/reset.rb +33 -0
- data/lib/studium/utility_scripts/show_descriptions_of_lectures_belonging_to_this_module/run.rb +50 -0
- data/lib/studium/utility_scripts/show_descriptions_of_lectures_belonging_to_this_module/show_descriptions_of_lectures_belonging_to_this_module.rb +145 -0
- data/lib/studium/utility_scripts/show_lecturers/show_lecturers.rb +147 -0
- data/lib/studium/utility_scripts/show_lectures/constants.rb +11 -0
- data/lib/studium/utility_scripts/show_lectures/help.rb +34 -0
- data/lib/studium/utility_scripts/show_lectures/initialize.rb +23 -0
- data/lib/studium/utility_scripts/show_lectures/menu.rb +127 -0
- data/lib/studium/utility_scripts/show_lectures/misc.rb +584 -0
- data/lib/studium/utility_scripts/show_lectures/reset.rb +89 -0
- data/lib/studium/utility_scripts/show_lectures/run.rb +27 -0
- data/lib/studium/utility_scripts/show_lectures/show_lectures.rb +48 -0
- data/lib/studium/utility_scripts/show_lectures_fitting_to_this_language/show_lectures_fitting_to_this_language.rb +121 -0
- data/lib/studium/utility_scripts/show_lectures_fitting_to_this_theme/show_lectures_fitting_to_this_theme.rb +105 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/constants.rb +17 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/determine.rb +673 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/help.rb +44 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/html.rb +605 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/initialize.rb +56 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/konsole.rb +32 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/menu.rb +472 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/misc.rb +837 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/reset.rb +121 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/run.rb +44 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/show.rb +106 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/show_lectures_on_the_commandline.rb +261 -0
- data/lib/studium/utility_scripts/show_lectures_on_the_commandline/sorted_individual_curricula.rb +121 -0
- data/lib/studium/utility_scripts/show_lectures_on_this_day.rb +149 -0
- data/lib/studium/utility_scripts/show_lva_dates_of_this_lecture.rb +169 -0
- data/lib/studium/utility_scripts/show_mixed_bachelor_master_courses/show_mixed_bachelor_master_courses.rb +91 -0
- data/lib/studium/utility_scripts/show_outdated_lva_dates/show_outdated_lva_dates.rb +210 -0
- data/lib/studium/utility_scripts/show_solved_english_lectures/show_solved_english_lectures.rb +139 -0
- data/lib/studium/utility_scripts/steop/README.md +4 -0
- data/lib/studium/utility_scripts/steop/show_all_steop_lectures.rb +93 -0
- data/lib/studium/utility_scripts/steop/steop_lectures_in_this_curriculum.rb +284 -0
- data/lib/studium/utility_scripts/steop/steop_lva_dates.rb +119 -0
- data/lib/studium/utility_scripts/studienkennzahl.rb +116 -0
- data/lib/studium/utility_scripts/studium_skeleton/studium_skeleton.rb +227 -0
- data/lib/studium/utility_scripts/stundenplan.rb +595 -0
- data/lib/studium/utility_scripts/sync_studium_relevant_entries_one_level_downwards.rb +217 -0
- data/lib/studium/utility_scripts/ufind/ufind.rb +98 -0
- data/lib/studium/utility_scripts/upcoming_mandatory_presence_courses/constants.rb +26 -0
- data/lib/studium/utility_scripts/upcoming_mandatory_presence_courses/run.rb +20 -0
- data/lib/studium/utility_scripts/upcoming_mandatory_presence_courses/upcoming_mandatory_presence_courses.rb +181 -0
- data/lib/studium/utility_scripts/week_parser/constants.rb +23 -0
- data/lib/studium/utility_scripts/week_parser/help.rb +32 -0
- data/lib/studium/utility_scripts/week_parser/menu.rb +59 -0
- data/lib/studium/utility_scripts/week_parser/misc.rb +373 -0
- data/lib/studium/utility_scripts/week_parser/reset.rb +65 -0
- data/lib/studium/utility_scripts/week_parser/run.rb +18 -0
- data/lib/studium/utility_scripts/week_parser/show.rb +236 -0
- data/lib/studium/utility_scripts/week_parser/week_parser.rb +49 -0
- data/lib/studium/utility_scripts/weekday_parser.rb +155 -0
- data/lib/studium/utility_scripts/weekly_schedule.rb +198 -0
- data/lib/studium/utility_scripts/wochenplanung.rb +261 -0
- data/lib/studium/version/version.rb +46 -0
- data/lib/studium/www/curricula_displayer.cgi +197 -0
- data/lib/studium/www/curriculum_displayer.rb +162 -0
- data/lib/studium/www/exams.cgi +53 -0
- data/lib/studium/www/fast_ask_exam_question.cgi +155 -0
- data/lib/studium/www/sinatra/app.rb +231 -0
- data/lib/studium/www/sinatra/misc.rb +115 -0
- data/lib/studium/www/statistics/statistics.cgi +59 -0
- data/lib/studium/yaml/ad_hoc_trainer/README.md +2 -0
- data/lib/studium/yaml/ad_hoc_trainer/exam_topics.md +15 -0
- data/lib/studium/yaml/allowed_themes_for_exams.yml +344 -0
- data/lib/studium/yaml/array_allowed_entries_for_the_file_lecture_information.yml +70 -0
- data/lib/studium/yaml/available_exam_topics/available_exam_topics.yml +234 -0
- data/lib/studium/yaml/backlog_of_exams.yml +37 -0
- data/lib/studium/yaml/colours/custom_colours.yml +28 -0
- data/lib/studium/yaml/colours/use_colours.yml +1 -0
- data/lib/studium/yaml/current_exams.yml +19 -0
- data/lib/studium/yaml/curricula/README.md +9 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_agrarwissenschaften_033255.yml +142 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_basisblock_033630.yml +65 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_botanik_033630.yml +84 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_ecology_033630.yml +74 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_mikrobiologie_und_genetik_033630.yml +120 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_molekulare_biologie_033630.yml +104 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_biologie_zoologie_033630.yml +87 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_chemie_033662.yml +165 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_dummy_curriculum.yml +183 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_elektrotechnik_und_informationstechnik_033235.yml +13 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_forstwirtschaft_033225.yml +115 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_informatik_033521.yml +130 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_ktww_033231.yml +84 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_lmbt_033217.yml +118 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_medizinische_informatik_033533.yml +203 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_molekularbiologie_033665.yml +95 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_nutrition_science_033638.yml +119 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_pharmazie_033305.yml +170 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_technische_chemie_033290.yml +129 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_technische_informatik_033535.yml +23 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_ubrm_033227.yml +136 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_verfahrenstechnik_033273.yml +167 -0
- data/lib/studium/yaml/curricula/bachelor/bachelor_wirtschaftsinformatik_033526.yml +29 -0
- data/lib/studium/yaml/curricula/individual/bachelor_informatik_und_molekulare_biologie.yml +1161 -0
- data/lib/studium/yaml/curricula/individual/bachelor_vector_based_strategies_in_life_sciences_molecular_medicine_and_biotechnology.yml +1157 -0
- data/lib/studium/yaml/curricula/individual/master_bioinformatics_and_nanobiotechnology_in_molecular_medicine.yml +306 -0
- data/lib/studium/yaml/curricula/individual/master_vector_based_strategies_in_life_sciences_molecular_medicine_and_biotechnology.yml +741 -0
- data/lib/studium/yaml/curricula/master/master_bioinformatik_066875.yml +76 -0
- data/lib/studium/yaml/curricula/master/master_biologie_molekulare_mikrobiologie_mikrobielle_oekologie_und_immunbiologie_066830.yml +78 -0
- data/lib/studium/yaml/curricula/master/master_biologische_chemie_066863.yml +61 -0
- data/lib/studium/yaml/curricula/master/master_dummy_curriculum.yml +197 -0
- data/lib/studium/yaml/curricula/master/master_genetik_und_entwicklungsbiologie_066877.yml +89 -0
- data/lib/studium/yaml/curricula/master/master_lmbt_066418.yml +111 -0
- data/lib/studium/yaml/curricula/master/master_molekulare_biologie_066834.yml +142 -0
- data/lib/studium/yaml/curricula/master/master_pharmazie_066605.yml +170 -0
- data/lib/studium/yaml/curricula/master/master_technische_chemie_066490.yml +123 -0
- data/lib/studium/yaml/curricula/outdated/master_bioinformatics_and_molecular_biotechnology_including_aspects_from_molecular_medicine.yml +438 -0
- data/lib/studium/yaml/curricula/outdated/master_food_science_and_plant_biotechnology.yml +31 -0
- data/lib/studium/yaml/curricula.yml +538 -0
- data/lib/studium/yaml/daily_questions_solved.yml +1468 -0
- data/lib/studium/yaml/default_delay.yml +4 -0
- data/lib/studium/yaml/default_encoding.yml +1 -0
- data/lib/studium/yaml/directory_to_the_exam_topics.yml +0 -0
- data/lib/studium/yaml/editor.yml +1 -0
- data/lib/studium/yaml/file_for_exam_questions.yml +1 -0
- data/lib/studium/yaml/german/README.md +2 -0
- data/lib/studium/yaml/german/german_to_english_month_names.yml +16 -0
- data/lib/studium/yaml/grouped_themes.yml +192 -0
- data/lib/studium/yaml/holidays.yml +194 -0
- data/lib/studium/yaml/important_exams.yml +226 -0
- data/lib/studium/yaml/inscription_dates_of_universities.yml +60 -0
- data/lib/studium/yaml/lecture_aliases.yml +138 -0
- data/lib/studium/yaml/lecture_information/lecture_information.yml +55870 -0
- data/lib/studium/yaml/log_dir.yml +1 -0
- data/lib/studium/yaml/main_topic.yml +11 -0
- data/lib/studium/yaml/max_stats.yml +241 -0
- data/lib/studium/yaml/meta_themes/README.md +13 -0
- data/lib/studium/yaml/meta_themes/biochemistry.md +6 -0
- data/lib/studium/yaml/meta_themes/bioinformatics.md +6 -0
- data/lib/studium/yaml/meta_themes/biotechnology.md +9 -0
- data/lib/studium/yaml/meta_themes/chemistry.md +9 -0
- data/lib/studium/yaml/meta_themes/genetics.md +10 -0
- data/lib/studium/yaml/meta_themes/immunology.md +5 -0
- data/lib/studium/yaml/meta_themes/metabolic_pathways.md +12 -0
- data/lib/studium/yaml/meta_themes/molecular_biology.md +9 -0
- data/lib/studium/yaml/meta_themes/protein_engineering.md +10 -0
- data/lib/studium/yaml/meta_themes/statistics.md +2 -0
- data/lib/studium/yaml/mitbelegung/README.md +4 -0
- data/lib/studium/yaml/mitbelegung/mitbelegung.yml +23 -0
- data/lib/studium/yaml/mitteilungsbl/303/244tter/mitteilungsbl/303/244tter.yml +363 -0
- data/lib/studium/yaml/n_total_questions.yml +1 -0
- data/lib/studium/yaml/rename_konsole_tab.yml +1 -0
- data/lib/studium/yaml/show_topic.yml +1 -0
- data/lib/studium/yaml/statistics/max_stats.yml +239 -0
- data/lib/studium/yaml/statistics/statistics.yml +69 -0
- data/lib/studium/yaml/week/01_monday.yml +5 -0
- data/lib/studium/yaml/week/02_tuesday.yml +75 -0
- data/lib/studium/yaml/week/03_wednesday.yml +62 -0
- data/lib/studium/yaml/week/04_thursday.yml +14 -0
- data/lib/studium/yaml/week/05_friday.yml +31 -0
- data/lib/studium/yaml/week/06_saturday.yml +16 -0
- data/lib/studium/yaml/week/07_sunday.yml +0 -0
- data/lib/studium/yaml/week/README.md +13 -0
- data/lib/studium.rb +5 -0
- data/studium.gemspec +80 -0
- data/test/testing_studium.rb +244 -0
- data/test/testing_studium_base_class.rb +17 -0
- data/test/testing_time_component.rb +29 -0
- metadata +1078 -0
data/README.md
ADDED
@@ -0,0 +1,2785 @@
|
|
1
|
+
[![forthebadge](https://forthebadge.com/images/badges/built-with-love.svg)](https://www.gobolinux.org/)
|
2
|
+
[![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
|
3
|
+
[![Gem Version](https://badge.fury.io/rb/studium.svg)](https://badge.fury.io/rb/studium)
|
4
|
+
|
5
|
+
This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">13.09.2022</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">01:32:52</span> o'clock.
|
6
|
+
|
7
|
+
<img src="https://i.imgur.com/9HrOT5B.png" style="border: 1px solid black">
|
8
|
+
<img src="https://i.imgur.com/tbKS413.png" style="margin-left: 0.3em">
|
9
|
+
<img src="https://i.imgur.com/vwo4UuK.jpg" style="border: 2px solid black">
|
10
|
+
<img src="https://i.imgur.com/Jcf9yoh.jpg" style="border: 3px solid black">
|
11
|
+
<img src="https://i.imgur.com/SSIPq4l.jpg" style="border: 3px solid black">
|
12
|
+
<img src="https://i.imgur.com/YG8V0hE.png" style="border: 3px solid black">
|
13
|
+
|
14
|
+
## Introduction to the studium-gem
|
15
|
+
|
16
|
+
Welcome to the legendary <span style="color: darkgreen; font-weight: bold">
|
17
|
+
Studium</span> project! This project makes our brains go <b>epic-mode</b>
|
18
|
+
(via oldschool training, though).
|
19
|
+
|
20
|
+
This is the documentation that refers to the 0.12.x release series. This
|
21
|
+
release series was started in **July 2022** and obsoleted the older
|
22
|
+
0.11.x release series that was started in <b>May 2022</b>.
|
23
|
+
|
24
|
+
The primary focus of the 0.11.x series was a clean-up - old code that
|
25
|
+
was no longer in use was removed. The primary focus of the 0.12.x
|
26
|
+
series, though, is to extend the project while doing clean-up work.
|
27
|
+
For instance, the java-bindings were started, and the ruby-libui
|
28
|
+
bindings were improved on windows in particular. In fact: libui
|
29
|
+
has been one big reason why the 0.12.x series was started. I really
|
30
|
+
wanted to solve the libui GUI situation finally, so that we can
|
31
|
+
use this project on windows as well.
|
32
|
+
|
33
|
+
On **rubygems.org** the 0.11.x release series will be made
|
34
|
+
available for a few more months. Consider updating to the
|
35
|
+
0.12.x release series when possible, though.
|
36
|
+
|
37
|
+
## Major and minor Goals and Objectives for the studium-gem
|
38
|
+
|
39
|
+
This subsection will attempt to detail what the point of
|
40
|
+
this project is. It will be a fairly long paragraph.
|
41
|
+
|
42
|
+
The **Studium project**, first and foremost, attempts to help
|
43
|
+
with **study-** and **exam-related topics** in general.
|
44
|
+
|
45
|
+
What is meant with this?
|
46
|
+
|
47
|
+
Well - consider you want to prepare for some exam, coming
|
48
|
+
in a few weeks. Perhaps you built some "flash card"
|
49
|
+
mnemonics to remember questions and associated answers
|
50
|
+
to these questions. You want to train your theoretical knowledge
|
51
|
+
in regards to these exam questions. Let's pick one exam
|
52
|
+
topic, say: **general chemistry**. Ok, so ...
|
53
|
+
|
54
|
+
You will probably learn more about atoms, the electrons
|
55
|
+
that can be found in these atoms, the chemical reactions
|
56
|
+
these may undergo.
|
57
|
+
|
58
|
+
From this point of view, the **studium** gem is somewhat
|
59
|
+
similar to other projects, such as **Studyflix** or
|
60
|
+
**StuDocu** - these projects may also try to be of help
|
61
|
+
in exam-related situations.
|
62
|
+
|
63
|
+
The **primary** purpose of the studium gem is to distribute the code
|
64
|
+
(in ruby, and to some extent in java), the associated dataset (mostly
|
65
|
+
text files, in particular yaml files) and also **interconnect** the
|
66
|
+
various ruby files that are distributed with this project under the
|
67
|
+
same "umbrella-project".
|
68
|
+
|
69
|
+
The main toplevel "namespace" for the **studium** gem, in ruby,
|
70
|
+
is **"module Studium"**.
|
71
|
+
|
72
|
+
The original goal for the **Studium project**, that is **why** it
|
73
|
+
was started, was to bundle together **knowledge** from different
|
74
|
+
topics - be these topics related to **ruby**, **informatics**,
|
75
|
+
**biology**, **chemistry**, **biotechnology**, **molecular
|
76
|
+
biology**, **virology** or **physics**, as an **exam trainer**
|
77
|
+
mostly.
|
78
|
+
|
79
|
+
The objective here in this regard, as a trainer-for-upcoming-exams,
|
80
|
+
was to improve the grades of the student at hand, and to be able
|
81
|
+
to pass more exams within a given time span, thus making the time
|
82
|
+
spent **more "efficient"** or worthwhile in this regard. (Evidently
|
83
|
+
the user still has to invest time into learning on his or her own,
|
84
|
+
so the studium-gem can only play a **supportive** role in this
|
85
|
+
regard; it can not replace one's own impetus for wanting to learn
|
86
|
+
more.)
|
87
|
+
|
88
|
+
Since then, this original use case has been **extended** quite a
|
89
|
+
lot, including online-related aspects (make the dataset available
|
90
|
+
via a web-interface, such as through sinatra), or via **GUI
|
91
|
+
bindings** (primarily via **ruby-gtk**, but also via **libui**).
|
92
|
+
|
93
|
+
The **Studium** gem is made up of several different classes, that
|
94
|
+
could potentially be of **help** to the user.
|
95
|
+
|
96
|
+
Note that not all the code may be needed for all use cases, so it
|
97
|
+
is recommended to focus only on those parts that may be relevant
|
98
|
+
for the user at hand, and simply ignore the other parts that seem
|
99
|
+
of no use. People are different, so they may need different parts
|
100
|
+
more so than others.
|
101
|
+
|
102
|
+
As a by-product of ruby being OOP-centric in nature, lots of
|
103
|
+
different classes may typically reside in the same
|
104
|
+
project; the studium project is no exception to that rule.
|
105
|
+
In the event that you are curious about these classes, feel
|
106
|
+
free to have a look at the right hand side of this gem's
|
107
|
+
homepage, the **Table of Contents**. The direct URL for
|
108
|
+
this is as follows:
|
109
|
+
|
110
|
+
https://www.rubydoc.info/gems/studium/
|
111
|
+
|
112
|
+
Furthermore, some classes are described in more detail in that
|
113
|
+
file here (**README.md**), or respectively doc/README.gen, which
|
114
|
+
is the template from which the **README.md** file is
|
115
|
+
autogenerated upon publishing a new version of this gem. However
|
116
|
+
had, do not expect a full explanation for all classes here; only
|
117
|
+
some classes will be discussed in more detail.
|
118
|
+
|
119
|
+
Note that there are **a LOT** of different classes and it is rather
|
120
|
+
unlikely that you will need all of them, so don't focus on all
|
121
|
+
classes with the assumption that they will all be equally useful.
|
122
|
+
Some of these classes have only **a very limited scope** and
|
123
|
+
use case, and thus are not too overly useful. Other classes are
|
124
|
+
more important, though, and the page here **attempts to focus
|
125
|
+
primarily on these more useful classes**, or rather, the
|
126
|
+
**functionality** that these classes ultimately provide. It is
|
127
|
+
hoped that this functionality may be of benefit to other people
|
128
|
+
as well.
|
129
|
+
|
130
|
+
But not every feature is described there; it would make the
|
131
|
+
listing way too long.
|
132
|
+
|
133
|
+
The **major** focus of the studium gem lies in regards to
|
134
|
+
"flashcards", mnemo-cards, anki-cards - aka entries that have
|
135
|
+
a registered **question**, and an **associated answer** to
|
136
|
+
that question. (anki-cards are a bit different in that they
|
137
|
+
focus on a **GUI** and allow such fancy things like embedding
|
138
|
+
pictures; the studium project here also has this as a minor
|
139
|
+
goal, but this comes **only** via GUI bindings, not the
|
140
|
+
commandline variant, obviously. It is of a lower priority,
|
141
|
+
though.)
|
142
|
+
|
143
|
+
These exam-related questions can be asked on the commandline,
|
144
|
+
via a **delay** - usually a three seconds delay, but this
|
145
|
+
can be toggled and changed by the end user on the commandline.
|
146
|
+
|
147
|
+
First, the question will appear on the commandline, and then,
|
148
|
+
after that specified **delay** has passed, the answer will be
|
149
|
+
revealed (and shown) on the commandline. This way the user can
|
150
|
+
improve his/her knowledge on a daily basis. In fact: although
|
151
|
+
I have not been studying at a university in many years, I
|
152
|
+
still use this project almost daily to expand my own local
|
153
|
+
knowledgebase.
|
154
|
+
|
155
|
+
You can query the current **set delay** via:
|
156
|
+
|
157
|
+
studium --delay?
|
158
|
+
|
159
|
+
Note that, in order for the question-answer "exam trainer" to work, you
|
160
|
+
need to have written down these questions and answers somewhere. By
|
161
|
+
default, I have bundled the dataset that I personally use, but this
|
162
|
+
will probably be very useless to most other people, so I recommend
|
163
|
+
to keep your own entries. (Many of my own entries are in german rather
|
164
|
+
than english, so ... feel free to re-use any of these questions as
|
165
|
+
you like to, if you find them useful. As of **March 2019**,
|
166
|
+
there are over **32.500** question-answers registered in the studium
|
167
|
+
project, in various different topics).
|
168
|
+
|
169
|
+
The **format** for question-answers is very simple:
|
170
|
+
|
171
|
+
- **One question** and **one answer** per given line. For example:
|
172
|
+
|
173
|
+
'- How does Rails call a "footer" on every page? "Partials".'
|
174
|
+
|
175
|
+
The above would constitute a question-answer exam entry.
|
176
|
+
|
177
|
+
The first part there constitutes the question; and the part after the
|
178
|
+
first '?' character is the answer. The '?' token is not mandatory though;
|
179
|
+
you can also substitute with 'A:' (which stands short for "Answer") and
|
180
|
+
not make use of '?' at all.
|
181
|
+
|
182
|
+
Note that any words enclosed in double quotes "" will be colourized differently
|
183
|
+
when displayed on the commandline. The reason for this is mostly so that it
|
184
|
+
provides a stronger visual cue as to what may be more important in the given
|
185
|
+
question/answer at hand. I found this helpful for memorizing when having these
|
186
|
+
questions asked on the commandline; for some reason my brain reacts more
|
187
|
+
strongly to colours. Probably does so for other people too, but again - if
|
188
|
+
you dislike anything there, you can (and should) always use your own
|
189
|
+
exam-dataset here.
|
190
|
+
|
191
|
+
## Namespaces in the project
|
192
|
+
|
193
|
+
The main namespace for this gem is simply called **Studium**, which is
|
194
|
+
german for **studies**. The gem could be renamed to **Studies** but
|
195
|
+
considering the fact that the original use case was for universities
|
196
|
+
in central europe, and many of the lectures stored in the main yaml
|
197
|
+
file are for lectures in german, I think it would make sense to retain
|
198
|
+
that name; you can always "alias" it like so, anyway:
|
199
|
+
|
200
|
+
Studies = Studium
|
201
|
+
|
202
|
+
The **exam-relevant part** resides under the **Studium::Exams** namespace.
|
203
|
+
So when you see that latter namespace, you know that it has to be code
|
204
|
+
that is specific to exams.
|
205
|
+
|
206
|
+
There are also some auxiliary classes, such as a primitive
|
207
|
+
"statistical analyzer" of some sort, to rate the performance
|
208
|
+
per day (from day to day, in regards to exam-questions that
|
209
|
+
were answered).
|
210
|
+
|
211
|
+
## Showing helpful information on the commandline
|
212
|
+
|
213
|
+
A **general overview on the commandline**, as to what the main
|
214
|
+
functionality is, can be obtained through this entry point,
|
215
|
+
aka **--help**:
|
216
|
+
|
217
|
+
studium --help
|
218
|
+
|
219
|
+
This will query **bin/studium**.
|
220
|
+
|
221
|
+
## Constants and toplevel-variables used in the Studium project
|
222
|
+
|
223
|
+
The Studium project makes use of lots of constants, in the ruby
|
224
|
+
code. This subsection mentions a few noteworthy ones - in particular
|
225
|
+
those that may be useful to know in some later situations when you
|
226
|
+
wish to "globally" change an aspect of the project.
|
227
|
+
|
228
|
+
The constant called MAKE_USE_OF_UNICODE_SYMBOLS_WHENEVER_POSSIBLE
|
229
|
+
refers to unicode symbols. Elements such as the right-facing arrow,
|
230
|
+
aka →. This can be useful as a visual cue.
|
231
|
+
|
232
|
+
If you wish to make use of more unicode symbols than retaining this
|
233
|
+
constant to true is good. This is the default value too (true).
|
234
|
+
|
235
|
+
A toplevel query method exists as well - see:
|
236
|
+
|
237
|
+
Studium.shall_we_make_use_of_unicode_symbols?
|
238
|
+
|
239
|
+
The old constant called ARRAY_EXCLUDE_THESE was removed for the 0.10.x
|
240
|
+
series. The old content was [ '[]','[skip]','[done]','X' ] but I
|
241
|
+
decided that a trailing [] is ideal. The trailing [] marks the
|
242
|
+
exam question at hand as "answered and thus solved". Back then I
|
243
|
+
experimented with different, simple ways to mark an exam question
|
244
|
+
as solved, but I came to the conclusion that a trailing " []"
|
245
|
+
is probably the best way to indicate that. A trailing "X" alone
|
246
|
+
can lead to confusion, when the answer itself has some upcased
|
247
|
+
characters near the end and such. A unicode symbol could be used,
|
248
|
+
but not every keyboard makes it easy to use that, so trailing
|
249
|
+
[] seems better. The other variants, such as [skip] or [done]
|
250
|
+
seem too long.
|
251
|
+
|
252
|
+
To query **where** the last exam question will be stored, use
|
253
|
+
this method:
|
254
|
+
|
255
|
+
Studium.file_last_question_asked? # => "/root/Studium/last_question_asked.md"
|
256
|
+
|
257
|
+
This could be used if you forgot which question was the last one
|
258
|
+
that was asked; or to automatically solve this question, via
|
259
|
+
other scripts in the **studium gem**.
|
260
|
+
|
261
|
+
There is a very important file, called **lecture_information.yml**.
|
262
|
+
|
263
|
+
Since that file is so important for the Studium project, a toplevel
|
264
|
+
instance variable keeps track of the path to this file (the **location**
|
265
|
+
to that file):
|
266
|
+
|
267
|
+
@file_lecture_information = nil # nil here means "not yet initialized to any value"
|
268
|
+
|
269
|
+
On my home system and home setup, I also keep all exam-files stored in a
|
270
|
+
specific location, which is revealed via:
|
271
|
+
|
272
|
+
Studium.file_exams? # => "/home/x/studium/YAML/exams.yml"
|
273
|
+
|
274
|
+
The path to this can be modified via:
|
275
|
+
|
276
|
+
Studium.set_file_exams()
|
277
|
+
Studium.set_file_exams(insert_path_here)
|
278
|
+
|
279
|
+
The Studium gem defaults to the UTF-8 encoding. As we require a bit
|
280
|
+
of flexibility here (some users may want to use another encoding),
|
281
|
+
the toplevel variable called **@use_this_encoding** stores which
|
282
|
+
encoding is to be used for all code and data within the studium
|
283
|
+
gem.
|
284
|
+
|
285
|
+
To query the current encoding in use, try this method:
|
286
|
+
|
287
|
+
Studium.encoding?
|
288
|
+
|
289
|
+
## Exam dataset
|
290
|
+
|
291
|
+
The **individual exam topics**, such as for **genetics** or **physics**
|
292
|
+
are stored in the subdirectory called <b>exam_topics/</b>.
|
293
|
+
|
294
|
+
I distribute the dataset for the topics that I have an interest in
|
295
|
+
with this gem, which explains why the gem is quite large. This dataset
|
296
|
+
will probably not be very useful for other people - after all you
|
297
|
+
may not necessarily share my own interest in different topics - but
|
298
|
+
if you want to use this project (such as for a base-system, and then
|
299
|
+
modify and adapt it to your needs) then you are very much encouraged
|
300
|
+
to build up your own dataset, anyway.
|
301
|
+
|
302
|
+
The primary reason as to why I have distributed my own dataset with
|
303
|
+
this gem is to simply show how it can be done; it is just more
|
304
|
+
convenient that way in the event that other people want to use the
|
305
|
+
project and adapt it to their own needs. It makes it easier for
|
306
|
+
people to figure out how to work with the project, by adding new
|
307
|
+
questions. And, of course, since I use the gem almost on a daily
|
308
|
+
basis, I polish the existing set of exam questions, so there is
|
309
|
+
some **quality control** ongoing here as well.
|
310
|
+
|
311
|
+
The **format** for these exams must be a **simple** one, that is - **one
|
312
|
+
question and one answer per registered line**. I currently encourage
|
313
|
+
you to use not more than **1000 question-answer entries per such a file**,
|
314
|
+
as it becomes unwieldy otherwise, but if you want to, you can ignore
|
315
|
+
this limitation as well. I just personally found it useful to have.
|
316
|
+
|
317
|
+
Whenever I have more than 1000 questions, I tend to **create a new
|
318
|
+
file** with "advanced" exam-questions, or simply split things up
|
319
|
+
in several different files. I did so for the metabolic pathways,
|
320
|
+
for instance, such as for glycolysis, the citric acid cycle,
|
321
|
+
and so forth. This started with a single file for **biochemistry**. Since
|
322
|
+
then I split it up into several sub-topics, such as **metabolism**,
|
323
|
+
**advanced biochemistry** and **aminoacids**, so the total question-answers
|
324
|
+
for biochemistry is close to about 4000 as of now. (It may be even more
|
325
|
+
than that if you also include molecular techniques and genetics into the
|
326
|
+
field of **biochemistry**, which some university lectures may do. But I
|
327
|
+
found it easier to use separate topics here, such as **genetics**,
|
328
|
+
**genomics** and **gene technology** instead.)
|
329
|
+
|
330
|
+
If you want to **query** which exam-topic is the current default (the
|
331
|
+
<b>current studyset</b>), then you can use the following invocation
|
332
|
+
on the commandline:
|
333
|
+
|
334
|
+
studium --current-studyset?
|
335
|
+
|
336
|
+
**How to best prepare for exams?**
|
337
|
+
|
338
|
+
This probably depends on the type of person you are, how your brain works,
|
339
|
+
how you memorize content. I can not give a general recommendation as to
|
340
|
+
how that should be for everyone - you need to determine this on your
|
341
|
+
own, for your particular case at hand.
|
342
|
+
|
343
|
+
But - what I believe may work very well for many different people, are
|
344
|
+
so called "flash-cards", that is: you have the question on one side,
|
345
|
+
and then the answer or answers on the other side of that card
|
346
|
+
(flip card). For looking at the answer you simply flip around the
|
347
|
+
card.
|
348
|
+
|
349
|
+
In my opinion, such mnemo cards or flash cards, are **quite effective**
|
350
|
+
and may also work for you. This was the primary goal for the studium
|
351
|
+
project too; it was built around that central concept for the most
|
352
|
+
part, at the least in regards to **exam questions**.
|
353
|
+
|
354
|
+
Note that the python-software **anki** (anki cards) uses a somewhat
|
355
|
+
related concept, although it is more sophisticated, e. g. you can
|
356
|
+
embed images into the dataset, and so forth.
|
357
|
+
|
358
|
+
## Flashcards (deprecated and removed)
|
359
|
+
|
360
|
+
Since as of **March 2018**, the studium project also supports
|
361
|
+
flashcards formally.
|
362
|
+
|
363
|
+
Flashcards are **mnemonic-cards**, where a question may be on the
|
364
|
+
front of a paper, and the answer to that question is on the backside.
|
365
|
+
|
366
|
+
Obviously computers can simulate this more easily without wasting
|
367
|
+
paper - but some people may prefer oldschool paper for memorizing
|
368
|
+
content.
|
369
|
+
|
370
|
+
At any rate, if you wish to add a new question-answer, then you
|
371
|
+
can use this commandline invocation:
|
372
|
+
|
373
|
+
flashcards add
|
374
|
+
|
375
|
+
You can also add a new question via the bin/studium file:
|
376
|
+
|
377
|
+
studium --add-a-new-question
|
378
|
+
|
379
|
+
Internally this will call class <b>AddExamQuestion</b>. As of
|
380
|
+
October 2020 I am not sure whether the namespace Flashcards
|
381
|
+
will be retained, though. We may have to look how useful these
|
382
|
+
flashcards are; at a later time it may be decided what to do
|
383
|
+
with that, but it could be removed as well.
|
384
|
+
|
385
|
+
In March 2022 support for flashcards in the above described
|
386
|
+
manner has been removed. Exam-question cards are similar to
|
387
|
+
flashcards, so the functionality is not completely gone -
|
388
|
+
but it is gone in the sense of "flashcard-centric design".
|
389
|
+
|
390
|
+
## The main dataset (Studium.main_dataset?)
|
391
|
+
|
392
|
+
The file called **lecture_information.yml** is the most important
|
393
|
+
yaml-file in this project. It stores all lectures that are tracked
|
394
|
+
by the studium-gem.
|
395
|
+
|
396
|
+
Loading a big yaml file can take some time. Having to do so again
|
397
|
+
and again may really slow down a project; it also makes little
|
398
|
+
sense to want to do so, because you already had to load it up
|
399
|
+
before, so why do it again?
|
400
|
+
|
401
|
+
Due to this situation, it seemed to make sense to allow a way to
|
402
|
+
store the dataset in an instance variable on the toplevel
|
403
|
+
namespace.
|
404
|
+
|
405
|
+
require 'studium/toplevel_methods/main_dataset.rb'
|
406
|
+
dataset = ::Studium.main_dataset? # ← Store it in a variable if you would like to.
|
407
|
+
|
408
|
+
## lecture_information.yml
|
409
|
+
|
410
|
+
The file <b>lecture_information.yml</b> is extremely important and rather
|
411
|
+
central to the studium gem, so this subsection will detail the rationale
|
412
|
+
for this file and what information can be found in that file.
|
413
|
+
|
414
|
+
The file **lecture_information.yml** is distributed as part of the **studium
|
415
|
+
gem**, in the <b>yaml/</b> **subdirectory** specifically. You can have a
|
416
|
+
look at it if you don't quite know the structure; perhaps use the editor
|
417
|
+
nano or vim or emacs for a quick look.
|
418
|
+
|
419
|
+
In order to obtain the **full path to this file**, via the commandline,
|
420
|
+
the following command can be used (**commandline instruction**):
|
421
|
+
|
422
|
+
studium --path-to-file-lecture-information
|
423
|
+
|
424
|
+
Essentially, lectures of universities can be **registered** in that file.
|
425
|
+
|
426
|
+
The basic **format** of that file is quite simple:
|
427
|
+
|
428
|
+
- The first line of every lecture-related entry, within enclosed "" quotes,
|
429
|
+
constitutes the **name** of the lecture. <b>Make sure that the name is
|
430
|
+
exactly, 1:1, the official name of the lecture at hand.</b> Make sure
|
431
|
+
that the name really is the name of the lecture, too - awkward errors
|
432
|
+
may otherwise be the consequence. From experience I can tell that the
|
433
|
+
more accurate the dataset is in that yaml file, the better.
|
434
|
+
|
435
|
+
Then, **additionally**, you must **prepend* the LV ID as the first entry
|
436
|
+
in that particular line.
|
437
|
+
|
438
|
+
Complete example for this follows:
|
439
|
+
|
440
|
+
<b>"301617 Strukturbiologie I":</b>
|
441
|
+
|
442
|
+
So - first comes the particular **LV ID** entry and then comes the
|
443
|
+
**name of the lecture**.
|
444
|
+
|
445
|
+
This is the **main entry** for that lecture in the **.yml** file.
|
446
|
+
|
447
|
+
Then, you can denote the content of the lecture at hand, via a
|
448
|
+
Hash. You can use !ruby/symbol to use a symbol; it is a yaml file
|
449
|
+
after all, with all pros and cons that come with it.
|
450
|
+
|
451
|
+
The **three main entries** are presently:
|
452
|
+
|
453
|
+
!ruby/symbol ects: 3.0
|
454
|
+
!ruby/symbol university: BOKU
|
455
|
+
!ruby/symbol language: german
|
456
|
+
|
457
|
+
More information can be added to describe the particular lecture
|
458
|
+
at hand. See the file
|
459
|
+
**studium/doc/documentation_for_the_file_lecture_information.md**
|
460
|
+
for more information pertaining to this.
|
461
|
+
|
462
|
+
Why is this information about the available lectures so important?
|
463
|
+
|
464
|
+
The information stored in the file **lecture_information.yml** is
|
465
|
+
important because it allows us to automatically calculate the ECTS
|
466
|
+
points in a given curriculum, and also keep track whether a
|
467
|
+
particular exam has already been passed successfully. (The latter
|
468
|
+
part has to be adjusted to your own exam-dataset of course;
|
469
|
+
it makes no sense for others to re-use my own dataset, as
|
470
|
+
that is specific to my use case. Obviously different people
|
471
|
+
will have totally other use cases.)
|
472
|
+
|
473
|
+
Some **helper classes** exist to sanitize or check the validity
|
474
|
+
of the information contained in that file. For example,
|
475
|
+
<b>class Studium::AutopurgeThisLectureDate</b> can be used to
|
476
|
+
purge outdated lva-entries from the file, allowing you to
|
477
|
+
more easily stay up-to-date with ongoing lectures.
|
478
|
+
|
479
|
+
(Obviously, for all of this to work, you need to have a
|
480
|
+
file that keeps track of these different lectures in the
|
481
|
+
first place.)
|
482
|
+
|
483
|
+
You can also check the validity of the file lecture_information.yml,
|
484
|
+
from the commandline, through
|
485
|
+
<b>class Studium::CheckTheLectureInformationFile</b>.
|
486
|
+
|
487
|
+
This can be invoked from the commandline as well:
|
488
|
+
|
489
|
+
studium --check-file-information
|
490
|
+
|
491
|
+
Note that you can also directly load the dataset from this file
|
492
|
+
via the following method:
|
493
|
+
|
494
|
+
Studium.lecture_information
|
495
|
+
|
496
|
+
## class Studium::FinishedExamsAtThisUniversity
|
497
|
+
|
498
|
+
class Studium::FinishedExamsAtThisUniversity can be used to show
|
499
|
+
which exams at a university have been passed successfully.
|
500
|
+
|
501
|
+
require 'studium/utility_scripts/finished_exams_at_this_university.rb'
|
502
|
+
Studium::FinishedExamsAtThisUniversity.new(ARGV)
|
503
|
+
Studium::FinishedExamsAtThisUniversity.new('uniwien')
|
504
|
+
Studium::FinishedExamsAtThisUniversity.new('tu')
|
505
|
+
|
506
|
+
Note that there are a few other classes that have a similar
|
507
|
+
functionality. It just seemed useful to also have an additional
|
508
|
+
class that is dedicated to that particular task.
|
509
|
+
|
510
|
+
## Regex-search for exams
|
511
|
+
|
512
|
+
You can search for passed exams via a "pseudo-regex", aka //
|
513
|
+
in a string:
|
514
|
+
|
515
|
+
studium /Partial name of exam goes in here/
|
516
|
+
studium /Elektronen/
|
517
|
+
studium /Bioinf/
|
518
|
+
|
519
|
+
Let's look at the last example, on the commandline. This will
|
520
|
+
send the first argument <b>"/Bioinf/"</b> to the ruby code that
|
521
|
+
handles the commandline. ARGV is an Array that will hold the
|
522
|
+
arguments given to a ruby .rb file as Strings, so we have a
|
523
|
+
pseudo-regex there - a String object that starts and ends with
|
524
|
+
the character '/'. We assume this String to be a regex, which
|
525
|
+
conveniently allows us to query for the name of passed exams.
|
526
|
+
|
527
|
+
This may be helpful if you want to find all exams that you have
|
528
|
+
passed successfully (and registered somewhere) but do not quite
|
529
|
+
remember the full name of the exam. Or, as in the last example,
|
530
|
+
to show all exams passed with a title that includes "Bioinf"
|
531
|
+
(meaning **Bioinformatics** or **Bioinformatik**).
|
532
|
+
|
533
|
+
Of course this should be tailored to your exams, not mine or
|
534
|
+
anyone else's exams. :)
|
535
|
+
|
536
|
+
You can also see the passed exams that belong to a given theme.
|
537
|
+
|
538
|
+
So for example, to show all exams that fit to the theme
|
539
|
+
"chemistry", you can use this call to output these exams:
|
540
|
+
|
541
|
+
studium --passed-exams=chemistry
|
542
|
+
|
543
|
+
## Flashcards / Mnemo-cards
|
544
|
+
|
545
|
+
The core of the studium project is to simulate the behaviour of
|
546
|
+
mnemo-cards, memo-cards or flashcards (we will assume these names
|
547
|
+
to be all <b>synonymous</b> to one another).
|
548
|
+
|
549
|
+
The project can thus ask the user a **random exam question**.
|
550
|
+
|
551
|
+
Then, if the correct answer to that exam question has been given,
|
552
|
+
this question can be marked as "solved" - the code for the
|
553
|
+
latter solved action resides in the file called **solved.rb**.
|
554
|
+
It can be used from the commandline, or simply use
|
555
|
+
**bin/solved** which provides this functionality.
|
556
|
+
|
557
|
+
Any exam question that has been marked as "solved" will no longer
|
558
|
+
be within the total pool of questions that the computer will ask
|
559
|
+
the user.
|
560
|
+
|
561
|
+
In other words, we can toggle on/off on a per question basis, via
|
562
|
+
a <b>trailing []</b> to a line in that file.
|
563
|
+
|
564
|
+
This allows you to systematically work through an exam dataset for
|
565
|
+
a given topic at hand.
|
566
|
+
|
567
|
+
Currently there is a cap in effect - 1000 questions to the same topic,
|
568
|
+
not more than that. This was mostly because I found it better to split
|
569
|
+
up the topics, e. g. "basic chemistry", and then "advanced chemistry",
|
570
|
+
and so on and so forth.
|
571
|
+
|
572
|
+
The exam dataset that I use myself is distributed with the studium
|
573
|
+
gem, but it is probably not very useful to other users. I recommend
|
574
|
+
that you maintain your own exam dataset - this will be much better
|
575
|
+
suited to your own needs, so me providing my own exam dataset is
|
576
|
+
mostly meant to serve as a "starter" for other people to do the
|
577
|
+
same.
|
578
|
+
|
579
|
+
## class Studium::AutoStud
|
580
|
+
|
581
|
+
The class AutoStud can automatically modify the cd_aliases yaml
|
582
|
+
file. cd_aliases are part of another project and bundle together
|
583
|
+
my cd-aliases, that is - aliases that help me navigate through
|
584
|
+
my local filesystem quickly. I make heavy use of aliases in
|
585
|
+
general.
|
586
|
+
|
587
|
+
If there is a file called exams.yml, then we can put numbers,
|
588
|
+
so called "tag-identifiers", into these. So for example, we
|
589
|
+
may have the entry '# === (13)' there. This means that
|
590
|
+
pwdstud13 is an alias to this directory, which will correspond
|
591
|
+
to an exam entry. These entries should be sorted in a way so
|
592
|
+
that entry 1 means the next upcoming exam, entry 2 the one
|
593
|
+
after that, and so forth and so on.
|
594
|
+
|
595
|
+
In the past, before 20.01.2018, I manually did most of the
|
596
|
+
work there - first, by modifying exams.yml, and then by
|
597
|
+
navigating towards the target directory, and then invoking
|
598
|
+
"newstud NUMBER" here, such as newstud 13. This was tedious
|
599
|
+
and somewhat error-prone, but mostly unnecessary. I then
|
600
|
+
created class AutoStud, which allowed me to navigate to
|
601
|
+
the directory at hand, and just take the name of the working
|
602
|
+
directory to determine the number. But even that was too
|
603
|
+
cumbersome, so I added a range specifier, such as:
|
604
|
+
|
605
|
+
autostud 1-15
|
606
|
+
|
607
|
+
This will, similar to a Range in ruby, work through from 1
|
608
|
+
to 15, and invoke class NewStud. This class is the one
|
609
|
+
that will modify the cd-aliases file.
|
610
|
+
|
611
|
+
Even the range specifier was unnecessary since I added:
|
612
|
+
|
613
|
+
autostud --max
|
614
|
+
|
615
|
+
This will automatically guess what is the max entry and use
|
616
|
+
that.
|
617
|
+
|
618
|
+
If the above subsection is a bit confusing, don't worry, it
|
619
|
+
really is simple once you understand it. It essentially
|
620
|
+
serves two purposes:
|
621
|
+
|
622
|
+
(a) to be able to show which exames are upcoming, via
|
623
|
+
say, <b>d25</b> (see bin/d25 for that)
|
624
|
+
(b) to just quickly navigate to these directories
|
625
|
+
for upcoming exams
|
626
|
+
|
627
|
+
I can then e. g. do "to4" to navigate to exam number 4
|
628
|
+
and look at the directory as to what material has been
|
629
|
+
collected for this exam.
|
630
|
+
|
631
|
+
Obviously this works for the exam dataset on my system -
|
632
|
+
you may have to maintain your own exams.yml file. I am
|
633
|
+
willing to make improvements to this part, both in
|
634
|
+
regards to code, but also in regards to the <b>documentation</b>.
|
635
|
+
|
636
|
+
## Determine which curricula are used for which lecture
|
637
|
+
|
638
|
+
One of the most important files for this project, file
|
639
|
+
<b>lecture_information.yml</b>, also contains the assigned
|
640
|
+
curricula for a given lecture at hand.
|
641
|
+
|
642
|
+
The class <b>Studium::DetermineCurricula</b> can then be used
|
643
|
+
to automatically output, on the commandline, in which curricula
|
644
|
+
a certain lecture is listed. This allows us to batch-calculate
|
645
|
+
the curricula used in an individual curriculum - e. g. if you
|
646
|
+
design such a curriculum, the class may help you to
|
647
|
+
automatically output from which other curricula certain lectures
|
648
|
+
were used/re-used. This constitutes the <b>"statistics"</b>
|
649
|
+
part of that class.
|
650
|
+
|
651
|
+
## class Studium::ForeignLanguagePercentage
|
652
|
+
|
653
|
+
class <b>Studium::ForeignLanguagePercentage</b> can be used
|
654
|
+
to show which lectures are in a given language, such as
|
655
|
+
the english language.
|
656
|
+
|
657
|
+
This requires that the entry called "!ruby/symbol language: english"
|
658
|
+
in the file <b>lecture_information.yml</b> has been set.
|
659
|
+
|
660
|
+
## class Studium::ShowLecturesOnTheCommandline
|
661
|
+
|
662
|
+
This class will show lectures that are part of the given
|
663
|
+
curriculum on the commandline. Additionally, a .html file
|
664
|
+
can be autogenerated (and will be opened in the browser,
|
665
|
+
if a certain constant has been set to true).
|
666
|
+
|
667
|
+
If a lecture has already been passed, then the remote URL
|
668
|
+
will not be shown. This behaviour can be overruled from
|
669
|
+
the commandline like so:
|
670
|
+
|
671
|
+
show_lectures_on_the_commandline --show-all-URLs --tuwienbiotech
|
672
|
+
|
673
|
+
This will show all remote URLs, even for lectures that were
|
674
|
+
already solved.
|
675
|
+
|
676
|
+
Do note that you can also design any arbitrary "curriculum"
|
677
|
+
on your own, and then load this dataset up.
|
678
|
+
|
679
|
+
Say that you have stored this into the file called **foo.md**.
|
680
|
+
|
681
|
+
To load this up, you can do:
|
682
|
+
|
683
|
+
studium --use-this-curriculum=foo.md
|
684
|
+
|
685
|
+
Remember to use only registered lectures (in the file
|
686
|
+
**lecture_information.yml**), and only one lecture per
|
687
|
+
line in that .md file (or any other text file).
|
688
|
+
|
689
|
+
## class Studium::ShowLectures
|
690
|
+
|
691
|
+
<b>class Studium::ShowLectures</b> will show lectures according
|
692
|
+
to a particular <b>theme</b>. For example, say that you want to
|
693
|
+
see all lectures that have something to do with
|
694
|
+
<b>"analytical chemistry"</b>.
|
695
|
+
|
696
|
+
You could then invoke this class and pass in a commandline option
|
697
|
+
such as the following one:
|
698
|
+
|
699
|
+
--analytical_chemistry
|
700
|
+
|
701
|
+
I have aliased the <b>show_lectures.rb file</b>, to the alias called
|
702
|
+
<b>show_lectures</b>, and then I can do this from the commandline:
|
703
|
+
|
704
|
+
show_lectures --analytical_chemistry
|
705
|
+
|
706
|
+
(Actually, I even have this aliased, to "tanalytical" - the
|
707
|
+
t stands for "theme". I use this for all the themes, e. g.
|
708
|
+
"tgenetics" for all themes belonging to the theme genetics,
|
709
|
+
"tinformatics" for all themes belonging to the theme
|
710
|
+
informatics, and so forth.)
|
711
|
+
|
712
|
+
This class will also show a split between bachelor and master
|
713
|
+
lectures. Bachelor lectures are shown first, then we will
|
714
|
+
show the lectures belonging to a master curriculum.
|
715
|
+
|
716
|
+
This class thus allows us to quickly find out which lectures
|
717
|
+
belong to a certain theme. It can then help when you wish
|
718
|
+
to create an individual curriculum based on one or several
|
719
|
+
<b>certain themes</b> - or when you simply want to see
|
720
|
+
which lectures are available belonging to a particular theme.
|
721
|
+
(I used it to see which exams I may do next, to fulfil a
|
722
|
+
certain theme criteria.)
|
723
|
+
|
724
|
+
Note that this class acts on information, which must have been
|
725
|
+
added prior to the file <b>lecture_information</b>, which is
|
726
|
+
also distributed with this project. Always keep that file
|
727
|
+
up to date - a lot of code in this project depends on that
|
728
|
+
file.
|
729
|
+
|
730
|
+
Since as of 10.03.2018, you can also pass in the options
|
731
|
+
--timetable or --upcoming. This will then autogenerate a
|
732
|
+
.html file listening the coming exams. That functionality
|
733
|
+
depends on class <b>ShowLecturesOnTheCommandline</b>.
|
734
|
+
|
735
|
+
## class Studium::Exams::Cycle
|
736
|
+
|
737
|
+
The class <b>Studium::Exams::Cycle</b> can be used to
|
738
|
+
cycle through the yaml file that holds which exams may
|
739
|
+
be upcoming.
|
740
|
+
|
741
|
+
Since as of March 2018, the yaml file is distributed with
|
742
|
+
the studium gem and can be found in the respective yaml
|
743
|
+
directory, such as at:
|
744
|
+
|
745
|
+
studium/yaml/current_exams.yml
|
746
|
+
|
747
|
+
Obviously if you wish to make use of it, you will have to
|
748
|
+
modify that file to fit your own preferences rather than
|
749
|
+
mine. This also depends on the exam topics that you want
|
750
|
+
to be exercising next.
|
751
|
+
|
752
|
+
The way how the class operates is really simple:
|
753
|
+
|
754
|
+
- After having asked one question from the current main
|
755
|
+
topic, the class will move towards the next topic at
|
756
|
+
hand, and so forth. When it reaches the "end", it will
|
757
|
+
resume at the beginning, so in other words this is a
|
758
|
+
cyclic array and the class operates via a "cyclic modus
|
759
|
+
operandi" - which thus explains he name of this class:
|
760
|
+
<b>Cycle</b>.
|
761
|
+
|
762
|
+
If you want to find out where the main .yml file resides,
|
763
|
+
you can do so via:
|
764
|
+
|
765
|
+
Studium::Exams::Cycle.main_file?
|
766
|
+
|
767
|
+
If you want to display which entries are part of the
|
768
|
+
current exam-cluster, you can do so from the commandline
|
769
|
+
via:
|
770
|
+
|
771
|
+
studium --collage?
|
772
|
+
|
773
|
+
## class Studium::ShowOutdatedLvaDates
|
774
|
+
|
775
|
+
<b>class Studium::ShowOutdatedLvaDates</b> can be used
|
776
|
+
to show which lectures (lva aka "lehrveranstaltung")
|
777
|
+
have outdated lva_dates entries.
|
778
|
+
|
779
|
+
That way the outdated entries can be updated (or removed).
|
780
|
+
|
781
|
+
This then allows other classes in the project to more
|
782
|
+
reliably show only lectures that are up-to-date.
|
783
|
+
|
784
|
+
You can also query this from the commandline via the <b>bin/studium</b>
|
785
|
+
executable, by issuing:
|
786
|
+
|
787
|
+
studium --outdated
|
788
|
+
|
789
|
+
## class Studium::ShowLecturesOnThisDay
|
790
|
+
|
791
|
+
This class will show all lectures that occur on a given day. The
|
792
|
+
format for that day must be in dd.mm.yyyy format such as
|
793
|
+
<b>18.06.2018</b>. (In the future this requirement may change
|
794
|
+
and allow for other formats, such as yyyy.mm.dd; but for now,
|
795
|
+
this is the only supported time format.)
|
796
|
+
|
797
|
+
The class will then proceed to check the file <b>lecture_information.yml</b>
|
798
|
+
for matching entries. If found, they will be retained and lateron
|
799
|
+
displayed, via the <b>.report</b> method.
|
800
|
+
|
801
|
+
You can either invoke the clas directly - it resides at
|
802
|
+
<b>studium/utility_scripts/show_lectures_on_this_day.rb</b> -
|
803
|
+
or you can invoke this functionality from the commandline.
|
804
|
+
|
805
|
+
The syntax for the commandline invocation can be in two formats.
|
806
|
+
|
807
|
+
studium --lectures-on-this-day=05.05.2018
|
808
|
+
studium 07.05.2018
|
809
|
+
|
810
|
+
The latter is significantly shorter and is recommended. It is the
|
811
|
+
current default action for input in the form dd.mm.yyyy. Do note
|
812
|
+
that this may, however had, also change in the future - but for
|
813
|
+
now (March 2018), this is the documented default behaviour for
|
814
|
+
input like the above. Use the more explicit one with the --
|
815
|
+
flags, since that one will be supported forever.
|
816
|
+
|
817
|
+
## class Studium::NExamsInTheseTopics
|
818
|
+
|
819
|
+
class <b>Studium::NExamsInTheseTopics</b> can report how many exam
|
820
|
+
topics are registered in the given input-topics at hand, and how many
|
821
|
+
of these were solved.
|
822
|
+
|
823
|
+
Several topics are combined together.
|
824
|
+
|
825
|
+
For example, for basic **biochemistry**, you can pass the argument
|
826
|
+
<b>meta_biochemistry</b> to this class, as a **String**.
|
827
|
+
|
828
|
+
class **Studium::NExamsInTheseTopics** will then output how many
|
829
|
+
questions were registered in that topic in total, and how many of
|
830
|
+
these questions were already solved.
|
831
|
+
|
832
|
+
For the "meta-topic" meta_biochemistry, we group together many
|
833
|
+
biochemistry-related topics - basic biochemistry, advanced
|
834
|
+
biochemistry, structural biology, proteomics, metabolism,
|
835
|
+
enzymes, glycolysis and so forth.
|
836
|
+
|
837
|
+
I created this class so that I can have a look at combined
|
838
|
+
topics. Otherwise it is quite similar to the statistics shown
|
839
|
+
when a single question is asked on the commandline, through
|
840
|
+
<b>class AskExamQuestion</b> (full name is:
|
841
|
+
<b>Studium::Exams::AskExamQuestion</b>).
|
842
|
+
|
843
|
+
Since as of August 2018, you can also use this as exam-trainer,
|
844
|
+
by providing the number of the sub-topic at hand.
|
845
|
+
|
846
|
+
So for example, if the main topic is meta-genetics, and
|
847
|
+
you pass in the argument 3, then the entry at the 3rd
|
848
|
+
place will be used as means to ask a question.
|
849
|
+
|
850
|
+
Examples:
|
851
|
+
|
852
|
+
metagen 2
|
853
|
+
metagen 5
|
854
|
+
|
855
|
+
Where "metagen" is my alias to:
|
856
|
+
|
857
|
+
n_exams_in_this_topic meta_genetics
|
858
|
+
|
859
|
+
By default, lines that end via "[]" are ignored, but you can also
|
860
|
+
ask a question from ALL available questions, even if they end
|
861
|
+
with a "[]" token.
|
862
|
+
|
863
|
+
Commandline example:
|
864
|
+
|
865
|
+
ask_exam_questions amg1 --all-questions
|
866
|
+
|
867
|
+
This would ask a random question from the **amg1-dataset**.
|
868
|
+
|
869
|
+
## class Studium::Exams::UpcomingExamsDataset
|
870
|
+
|
871
|
+
The **class Studium::Exams::UpcomingExamsDataset** is a **helper**-class.
|
872
|
+
|
873
|
+
It wraps over the file <b>exams.yml</b> and allows a simple query to
|
874
|
+
the upcoming exams, based on that file (which, as exam, must be
|
875
|
+
registered in the file <b>exams.yml</b>).
|
876
|
+
|
877
|
+
This information can then be used to query which exams are upcoming
|
878
|
+
on which day, at which time. This information can also be re-used
|
879
|
+
in different classes, which was one important reason as to why
|
880
|
+
this class has been created in the first place.
|
881
|
+
|
882
|
+
## Studium.pristine
|
883
|
+
|
884
|
+
The toplevel-method made available through <b>Studium.pristine</b>
|
885
|
+
can be used to create a new <b>lecture_information</b> file,
|
886
|
+
from scratch.
|
887
|
+
|
888
|
+
The one that is, by default, bundled with the studium-gem is/was
|
889
|
+
tailored to my own needs and use case. So if you want to use the
|
890
|
+
file, it may be better to generate it once, and then modify that
|
891
|
+
newly generated file on your own. (Don't forget to keep a backup
|
892
|
+
of it available as well, in case it is deleted or overwritten
|
893
|
+
accidentally.)
|
894
|
+
|
895
|
+
Note that you can invoke **Studium.pristine()** via the
|
896
|
+
commandline as well, via:
|
897
|
+
|
898
|
+
studium --pristine
|
899
|
+
studium --new-lecture-information
|
900
|
+
|
901
|
+
You can then copy this file into the default location, where
|
902
|
+
the file <b>lecture_information.yml</b> is normally stored,
|
903
|
+
via:
|
904
|
+
|
905
|
+
studium --merge
|
906
|
+
|
907
|
+
## Commandline examples of the studium gem
|
908
|
+
|
909
|
+
This subsection shows some commandline examples, in a succinct
|
910
|
+
manner.
|
911
|
+
|
912
|
+
Display **bachelor curricula**, via the syntax --bachelor=NAME_HERE
|
913
|
+
|
914
|
+
studium --bachelor=vektorx
|
915
|
+
studium --bachelor=genetics
|
916
|
+
|
917
|
+
Display **master curricula**, via the syntax --master=NAME_HERE
|
918
|
+
|
919
|
+
studium --master=vektorx
|
920
|
+
studium --master=immunobio
|
921
|
+
|
922
|
+
Note that in both cases, the curriculum has to be registered.
|
923
|
+
|
924
|
+
If you wish to see which exams have been passed, that is,
|
925
|
+
completed successfully, then use this invocation style:
|
926
|
+
|
927
|
+
studium --passed-exams?
|
928
|
+
studium --passed-exams
|
929
|
+
|
930
|
+
If you want to show how many ECTS points have been completed
|
931
|
+
in the registered curricula, do either of the following:
|
932
|
+
|
933
|
+
studium --passed-ects?
|
934
|
+
studium --passed-ects
|
935
|
+
|
936
|
+
To show how many question-answers I added per year, on my
|
937
|
+
own exam dataset, this can be used:
|
938
|
+
|
939
|
+
studium --questions-per-year
|
940
|
+
|
941
|
+
## Studium.return_div_timetable_of_upcoming_exams
|
942
|
+
|
943
|
+
This module-method can show the upcoming exams, as a html table.
|
944
|
+
|
945
|
+
This allows you to look at the upcoming exams in a <b>browser</b>.
|
946
|
+
|
947
|
+
The priority of the given lecture must be among these values:
|
948
|
+
|
949
|
+
1, 2, 3, 4, 5
|
950
|
+
|
951
|
+
Thus, a priority value of higher than 5 will <b>not</b> be
|
952
|
+
shown/considered.
|
953
|
+
|
954
|
+
## Aliases
|
955
|
+
|
956
|
+
The studium-gem uses several aliases. These exist mostly for
|
957
|
+
convenience.
|
958
|
+
|
959
|
+
For example, bin/studium has an entry point called <b>--master-curricula</b>.
|
960
|
+
This variant also works via <b>--master</b> alone. The latter option
|
961
|
+
is not explicitely mentioned since it is just an alias. If you think
|
962
|
+
that a specific alias is missing, let me know and I will add it (as
|
963
|
+
long as it does not conflict with any other entry point.)
|
964
|
+
|
965
|
+
## Return all passed exams
|
966
|
+
|
967
|
+
If you need to obtain a list (an <b>Array</b>) of all exams passed,
|
968
|
+
you can use any of the following two methods:
|
969
|
+
|
970
|
+
Studium.all_passed_exams
|
971
|
+
Studium.return_all_passed_exams
|
972
|
+
|
973
|
+
On the commandline, you can invoke this via:
|
974
|
+
|
975
|
+
studium --passed-exams
|
976
|
+
studium --all-passed-exams
|
977
|
+
studium --return-all-passed-exams
|
978
|
+
|
979
|
+
Note that this will <b>only</b> honour exams that have been
|
980
|
+
registered in the file <b>lecture_information.yml</b>.
|
981
|
+
|
982
|
+
To show how many ECTS you have passed in all curricula,
|
983
|
+
use this method:
|
984
|
+
|
985
|
+
Studium.show_passed_credits_per_curriculum
|
986
|
+
|
987
|
+
## curricula.yml and registered curricula
|
988
|
+
|
989
|
+
The file <b>curricula.yml</b> collects the <b>id-numbers</b> of different
|
990
|
+
bachelor/master curricula, from <b>different universities</b>, in
|
991
|
+
<b>Austria</b>. It can be found under the <b>yaml/</b> subdirectory.
|
992
|
+
|
993
|
+
In theory this file could be extended to also include EU-wide curricula
|
994
|
+
listed, but I only limited it to my own potential use cases or that of
|
995
|
+
(former) colleagues.
|
996
|
+
|
997
|
+
If other people want to add different curricula numbers, subdirectories
|
998
|
+
may have to be created for each country - but for now, since nobody else
|
999
|
+
may need more curricula, the current structure will remain as it is.
|
1000
|
+
|
1001
|
+
Do also note that within the <b>yaml/ subdirectory</b>, there is another
|
1002
|
+
directory called <b>curricula/</b>. The latter directory includes
|
1003
|
+
several curricula with the respective lectures that belong to
|
1004
|
+
this particular curriculum. These files are used to keep track of
|
1005
|
+
which lectures are part of these curricula and whether you have already
|
1006
|
+
successfully passed these or whether you have not.
|
1007
|
+
|
1008
|
+
## Grades
|
1009
|
+
|
1010
|
+
Exams at universities are typically graded. Different countries make
|
1011
|
+
use of different systems. For example, germany uses 6 grades whereas
|
1012
|
+
Austria uses 5 grades.
|
1013
|
+
|
1014
|
+
If you want to output which exams fit to a certain grade, such as
|
1015
|
+
<b>grade 2</b>, then you can use code written in
|
1016
|
+
<b>studium/toplevel_methods/show_passed_exams_having_this_grade.rb</b>:
|
1017
|
+
|
1018
|
+
The API is:
|
1019
|
+
|
1020
|
+
Studium.show_passed_exams_having_this_grade
|
1021
|
+
Studium.show_passed_exams_having_this_grade(2)
|
1022
|
+
Studium.show_passed_exams_having_this_grade(3)
|
1023
|
+
Studium.show_passed_exams_having_this_grade(4)
|
1024
|
+
|
1025
|
+
Simply pass the <b>number</b> to that method, corresponding to the
|
1026
|
+
grade that is sought. In order for this to work, you must use some
|
1027
|
+
file where the grades are stored. This can be either in the file
|
1028
|
+
<b>lecture_information.yml</b> (I recommend this approach), but it
|
1029
|
+
could also be a local .csv file. (The latter is mostly still there
|
1030
|
+
for legacy reasons; when this project was started, a .csv file was
|
1031
|
+
used rather than a .yml file. Lateron it was realized that the yaml
|
1032
|
+
file would be much better, since it can also include native and
|
1033
|
+
nested data structures, which makes it a lot easier to parse
|
1034
|
+
as-is, via the yaml wrapper that ruby has.)
|
1035
|
+
|
1036
|
+
## Improving this project
|
1037
|
+
|
1038
|
+
If other people would like to make use of this this project, I am open
|
1039
|
+
for suggestions on how to make it more flexible.
|
1040
|
+
|
1041
|
+
Otherwise, I will just keep it here as it is, as I do (or rather, did)
|
1042
|
+
require it in a few of my other projects. And if nobody else uses it
|
1043
|
+
then this is also fine because I used to be the number one user here
|
1044
|
+
anyway - the project had to solve existing problems, and it did so
|
1045
|
+
fairly well. Extra work past this point (in the year **2018**) is
|
1046
|
+
mostly done just to polish existing functionality, and to add a
|
1047
|
+
tiny bit of new functionality every now and then, or to improve the
|
1048
|
+
documentation. :)
|
1049
|
+
|
1050
|
+
I am also adding some code now and then for GUI and www-related use,
|
1051
|
+
as this interests me personally; but other than that, I consider the
|
1052
|
+
project mostly "done" in regards to time investment.
|
1053
|
+
|
1054
|
+
## The method obtain_this_value_from_hash()
|
1055
|
+
|
1056
|
+
This method resides in the file <b>studium/base/base.rb</b>.
|
1057
|
+
|
1058
|
+
It was created in order to access the main Hash - that is, the
|
1059
|
+
Hash that is returned from the file <b>lecture_information.yml</b>.
|
1060
|
+
|
1061
|
+
I had to access the various entries from said file and this was
|
1062
|
+
becoming a bit tedious. It became even more tedious because some
|
1063
|
+
keys are Strings and some keys are Symbols. Since I did not want
|
1064
|
+
to look up all the time whether I am dealing with Strings or
|
1065
|
+
with Symbols, I transitioned into using that method instead.
|
1066
|
+
|
1067
|
+
It is thus a bit similar to <b>HashWithIndifferentAccess</b>, except
|
1068
|
+
that it is just a simple method (and the main name is actually
|
1069
|
+
<b>obtain()</b>).
|
1070
|
+
|
1071
|
+
## Download the exam dataset
|
1072
|
+
|
1073
|
+
You can download the exam dataset by making use of this commandline
|
1074
|
+
option:
|
1075
|
+
|
1076
|
+
studium --download-exam-dataset
|
1077
|
+
studium --download-dataset
|
1078
|
+
|
1079
|
+
This will copy into the exam_topics/ subdirectory, so make sure
|
1080
|
+
that you want this BEFORE calling the above. If in doubt, backup
|
1081
|
+
your exam dataset and store it elsewhere on top of that (which
|
1082
|
+
may be a good idea in general).
|
1083
|
+
|
1084
|
+
## class Studium::ShowLecturesOfThisCurriculumId
|
1085
|
+
|
1086
|
+
**class Studium::ShowLecturesOfThisCurriculumId** can be used to output
|
1087
|
+
all lectures that **belong to a particular curriculum ID**. That way
|
1088
|
+
you can see which lectures could be done for a particular curriculum;
|
1089
|
+
and which lectures have already been passed in this curriculum, too.
|
1090
|
+
|
1091
|
+
You can input either the curriculum ID to this class; or some
|
1092
|
+
shortcuts.
|
1093
|
+
|
1094
|
+
The following input works on my home system, where
|
1095
|
+
show_lectures_of_this_curriculum_id is alias to the .rb file that
|
1096
|
+
holds **class Studium::ShowLecturesOfThisCurriculumId** can be used to output:
|
1097
|
+
|
1098
|
+
show_lectures_of_this_curriculum_id 066875
|
1099
|
+
show_lectures_of_this_curriculum_id Bioinformatik
|
1100
|
+
show_lectures_of_this_curriculum_id MolBio
|
1101
|
+
show_lectures_of_this_curriculum_id Landschaftsplanung
|
1102
|
+
|
1103
|
+
## Description of lectures
|
1104
|
+
|
1105
|
+
Some lectures are described in the file **lecture_information.yml**, but not
|
1106
|
+
all are. I have described only some which were of relevance to me. Most of
|
1107
|
+
these descriptions are in german, because the teaching language for most of
|
1108
|
+
these lectures is in german.
|
1109
|
+
|
1110
|
+
If you ever want to add your own descriptions, you can do so, by populating
|
1111
|
+
the entry called:
|
1112
|
+
|
1113
|
+
!ruby/symbol description: |
|
1114
|
+
|
1115
|
+
## KDE Konsole support
|
1116
|
+
|
1117
|
+
In the past we could rename KDE Konsole tabs, but this behaviour is presently
|
1118
|
+
(November 2018) slightly buggy. I have thus disabled it.
|
1119
|
+
|
1120
|
+
It may be re-enabled one day in the future, but via a configuration setting,
|
1121
|
+
so that users can disable/enable it. By default it will then be disabled.
|
1122
|
+
|
1123
|
+
## Studium::PassedEctsPerYear
|
1124
|
+
|
1125
|
+
If you need to find out how many ECTS points have been passed per given
|
1126
|
+
year for a particular curriculum then you can use class
|
1127
|
+
**Studium::PassedEctsPerYear**.
|
1128
|
+
|
1129
|
+
The input is the name of that curriculum. Obviously for this to work, the
|
1130
|
+
curriculum has had to be registered first.
|
1131
|
+
|
1132
|
+
You can also invoke it from the commandline, via:
|
1133
|
+
|
1134
|
+
studium --passed-ects-per-year
|
1135
|
+
|
1136
|
+
## Display the amount of ECTS points passed in Bachelor/Master lectures
|
1137
|
+
|
1138
|
+
You can find out how many ECTS points were passed in Bachelor and
|
1139
|
+
Master lectures so far via:
|
1140
|
+
|
1141
|
+
studium --ects-bachelor-master
|
1142
|
+
|
1143
|
+
## Using an environment variable to specify your replacement for lecture_information.yml
|
1144
|
+
|
1145
|
+
Some people may wish to use the project but wish to use another .yml
|
1146
|
+
file, other than the default one called **lecture_information.yml**.
|
1147
|
+
This is normally done so that you can, for example, add your own exam
|
1148
|
+
dataset into this .yml file (and have it persistent, that is, stored
|
1149
|
+
somewhere else on your filesystem, rather than use the bundled
|
1150
|
+
variant that comes distributed with the **studium** gem itself).
|
1151
|
+
|
1152
|
+
For people who require this, there exists an **environment variable**
|
1153
|
+
called **STUDIUM_FILE_LECTURE_INFORMATION**. Simply assign to this
|
1154
|
+
variable the full path to your dataset, which must be a .yml file
|
1155
|
+
in the same format.
|
1156
|
+
|
1157
|
+
Example for bash:
|
1158
|
+
|
1159
|
+
STUDIUM_FILE_LECTURE_INFORMATION=/opt/foo/bar.yml
|
1160
|
+
|
1161
|
+
## class Studium::ShowCompletedEctsInAllCurricula
|
1162
|
+
|
1163
|
+
**class Studium::ShowCompletedEctsInAllCurricula** can be used
|
1164
|
+
to show the completed ECTS per curriculum, sorted by n ECTS (maximum
|
1165
|
+
amount of ECTS) first. This is really just an "overview" class that
|
1166
|
+
shall quickly tell you how many different curricula exist.
|
1167
|
+
|
1168
|
+
A threshold value ("cut off") exists, which is set to 5.0 ECTS
|
1169
|
+
by default. Only if you have passed exams worth a total of at
|
1170
|
+
the least 5.0 ECTS will they be shown. This is set via a constant
|
1171
|
+
which can be toggled.
|
1172
|
+
|
1173
|
+
## class Studium::ShowConflictingLvaLectures
|
1174
|
+
|
1175
|
+
**class Studium::ShowConflictingLvaLectures** resides at the internal
|
1176
|
+
location <b>studium/utility_scripts/show_conflicting_lva_lectures.rb</b>,
|
1177
|
+
within the **studium** gem.
|
1178
|
+
|
1179
|
+
The purpose of this class is to **show conflicting lva-lecture dates**.
|
1180
|
+
|
1181
|
+
For example, say that you want to know whether there are any conflicts on
|
1182
|
+
the day **16.10.2018** (16th October in the year **2018**). Then you would
|
1183
|
+
simply pass that string into <b>class Studium::ShowConflictingLvaLectures</b>
|
1184
|
+
and that class will then display which exams and which lectures are on
|
1185
|
+
that date, **sorted by time**.
|
1186
|
+
|
1187
|
+
Example:
|
1188
|
+
|
1189
|
+
conflict 16.10.2018
|
1190
|
+
|
1191
|
+
(I use the alias called **conflict** to invoke that .rb file from the
|
1192
|
+
commandline.)
|
1193
|
+
|
1194
|
+
You can pass in any number of dates in the **dd.mm.yyyy** format, and the
|
1195
|
+
class will iterate through all of them and report which lectures and
|
1196
|
+
exams happen on each respective day.
|
1197
|
+
|
1198
|
+
You can use a range of dates too, if you pass in a **-** between two
|
1199
|
+
such dates.
|
1200
|
+
|
1201
|
+
Example:
|
1202
|
+
|
1203
|
+
conflict 16.10.2018-20.10.2018
|
1204
|
+
|
1205
|
+
This will be treated as if you would have given input from the
|
1206
|
+
16th, 17th, 18th, 19th and 20th. That can thus be used as a
|
1207
|
+
sort of "mini-calendar", on the commandline, in regards to
|
1208
|
+
important lectures/exams. (Remember that you will have to
|
1209
|
+
populate and maintain the dataset in the file called
|
1210
|
+
**lecture_information.yml** for this to work.)
|
1211
|
+
|
1212
|
+
You can also use a few **abbreviations** for **class Studium::ShowConflictingLvaLectures**.
|
1213
|
+
|
1214
|
+
For example, the capital letter **A** is a hardcoded entry that I may
|
1215
|
+
change to indicate which is the starting day of university in a given
|
1216
|
+
semster, such as **01.10.2018** or any such day. The capital letter B
|
1217
|
+
then refers to the day after that day, the capital letter C refers to
|
1218
|
+
the day after B, and so forth. The idea here is to use just a one-letter
|
1219
|
+
abbreviation rather than have to input **4 - 10** characters instead.
|
1220
|
+
|
1221
|
+
As already stated in this subsection, the file **lecture_information.yml**
|
1222
|
+
needs to have these lectures/exams registered first, before <b>class
|
1223
|
+
Studium::ShowConflictingLvaLectures</b> is able to display them.
|
1224
|
+
|
1225
|
+
Why was this class added? I needed that functionality to plan **exam-dates**
|
1226
|
+
ahead of time. That way I could display which exams may be upcoming
|
1227
|
+
and so forth - helped me in regards to **time management**.
|
1228
|
+
|
1229
|
+
## Underline-support for exam questions
|
1230
|
+
|
1231
|
+
You can use **ud**test**/ud** or **u**test**/u** to use underline-support
|
1232
|
+
in KDE konsole for question-answer combinations. (I can not use tags
|
1233
|
+
here in markdown, or so it seems, so assume that **ud** stands for the
|
1234
|
+
corresponding tag.)
|
1235
|
+
|
1236
|
+
## Studium::ShowLecturers
|
1237
|
+
|
1238
|
+
class **Studium::ShowLecturers** will show the lecturers of each lecture
|
1239
|
+
in a given curriculum, on the commandline/terminal.
|
1240
|
+
|
1241
|
+
If an entry is missing the lectures then this will be reported on
|
1242
|
+
the commandline.
|
1243
|
+
|
1244
|
+
The idea behind this class is mostly to allow you to quickly find out
|
1245
|
+
which lecturer holds which particular lecture (and when).
|
1246
|
+
|
1247
|
+
It is not a too terribly useful class, though - mostly exists just
|
1248
|
+
for **sake of completeness**.
|
1249
|
+
|
1250
|
+
## Registered URL entries to the (registered) lectures
|
1251
|
+
|
1252
|
+
Since as of 15.04.2019 (April 2019) it is possible to
|
1253
|
+
return the remote URL of a given registered lecture,
|
1254
|
+
through the **Studium** module.
|
1255
|
+
|
1256
|
+
Let's first show an example for this:
|
1257
|
+
|
1258
|
+
Studium.return_remote_homepage_of_this_lecture "270016 Massenspektrometrie" # => "https://ufind.univie.ac.at/de/course.html?lv=270016&semester=2019S"
|
1259
|
+
Studium.return_remote_homepage_of_this_lecture "Massenspektrometrie" # => "https://ufind.univie.ac.at/de/course.html?lv=270016&semester=2019S"
|
1260
|
+
|
1261
|
+
As you may be able to see, we take a shorter input string,
|
1262
|
+
aka the name of the lecture at hand, and then return the
|
1263
|
+
remote URL for that lecture.
|
1264
|
+
|
1265
|
+
This requires that there is a key called :homepage registered
|
1266
|
+
for that particular lecture in the file **lecture_information.yml**.
|
1267
|
+
|
1268
|
+
Right now only a very few lectures contain such an entry, but I
|
1269
|
+
will extend on this slowly, as time permits. The long term goal
|
1270
|
+
will be to provide a remote URL to **all** registered lectures.
|
1271
|
+
(This was already possible through the BeautifulUrl project,
|
1272
|
+
but I realized that it may be better to a) register this directly
|
1273
|
+
within the Studium project and b) to not depend on other projects
|
1274
|
+
if possible).
|
1275
|
+
|
1276
|
+
## Encoding
|
1277
|
+
|
1278
|
+
The default encoding for the **Studium** gem used to be
|
1279
|
+
the **encoding ISO-8859-1**, aliased onto the constant
|
1280
|
+
called **ENCODING_ISO**. This setting (constant) can be found
|
1281
|
+
in the file **studium/encoding/encodings.rb**
|
1282
|
+
|
1283
|
+
Since as of **May 2019** the default encoding is now **UTF-8**.
|
1284
|
+
|
1285
|
+
In the event that you may wish to use another encoding, you
|
1286
|
+
can modify the yaml file called <b>default_encoding.yml</b>,
|
1287
|
+
at **studium/yaml/default_encoding.yml**. Simply add the name
|
1288
|
+
of the constant there.
|
1289
|
+
|
1290
|
+
The reason why I personally used **ISO-8859-1** as encoding is because
|
1291
|
+
german umlauts can be a hassle under UTF when combined with an
|
1292
|
+
old editor I used to use. I finally abandoned that editor in 2019
|
1293
|
+
and am now using another editor, so it was also possible to
|
1294
|
+
switch to UTF-8. Unicode/UTF has quite a massive
|
1295
|
+
<b>intrinsic complexity</b>, but it also has some useful things,
|
1296
|
+
such as emojis and unicode characters, which can be used on the
|
1297
|
+
terminal in a colourized manner. That was actually the primary
|
1298
|
+
reason why I switched into UTF-8, as odd as that may sound.
|
1299
|
+
|
1300
|
+
The Studium project will continue to allow any other encoding
|
1301
|
+
though, as long as it is supported by ruby itself.
|
1302
|
+
|
1303
|
+
For the time being, there also exists a commandline way to change
|
1304
|
+
the encoding in use for the Studium project.
|
1305
|
+
|
1306
|
+
studium --encoding=utf
|
1307
|
+
studium --encoding=iso1
|
1308
|
+
|
1309
|
+
If you are fine with UTF-8 then obviously you do not have to change
|
1310
|
+
anything.
|
1311
|
+
|
1312
|
+
## Studium::SolvedEctsPerUniversity
|
1313
|
+
|
1314
|
+
If you have solved ECTS credits at different universities, and
|
1315
|
+
registered this in the file **lecture_information.yml**, then
|
1316
|
+
this class will give a little summary on the commandline as to
|
1317
|
+
the number of ECTS points solved at different universities.
|
1318
|
+
|
1319
|
+
## Logging activities done within the Studium project
|
1320
|
+
|
1321
|
+
The **Studium project** will try, by default, to log a lot of
|
1322
|
+
information that may be useful in some cases. This is not a
|
1323
|
+
trivial task, because there are many different classes that
|
1324
|
+
make up this project.
|
1325
|
+
|
1326
|
+
The paragraph here aims to explain some of the rationale behind
|
1327
|
+
the logging.
|
1328
|
+
|
1329
|
+
class **Studium::Log::StoreLastQuestionAskedIntoFile** will store
|
1330
|
+
the last exam-question asked into a file, together with the time
|
1331
|
+
stamp. This can then be used to answer questions such as "have I
|
1332
|
+
already asked myself this question today?". So this may help
|
1333
|
+
for training purposes, e. g. when you wish to acquire some knowledge,
|
1334
|
+
and learn for new questions that way.
|
1335
|
+
|
1336
|
+
## Studium.find_corresponding_exam_topic
|
1337
|
+
|
1338
|
+
The toplevel method <b>Studium.find_corresponding_exam_topic</b> is
|
1339
|
+
mostly a convenience method. It will accept an input, ideally
|
1340
|
+
a **String**, and return back the **official, registered name
|
1341
|
+
of the particular exam topic at hand**.
|
1342
|
+
|
1343
|
+
For example, 'genetik' as input to this method will become
|
1344
|
+
'allgemeine_genetik', which is also the locally existing
|
1345
|
+
name for the exam-file at hand.
|
1346
|
+
|
1347
|
+
The idea behind that method is that we can take a shorter
|
1348
|
+
input, and still obtain the real filename. This is convenient
|
1349
|
+
because you can type just a few characters, and have the
|
1350
|
+
name of the exam-file returned. It allows us to be lazy here.
|
1351
|
+
|
1352
|
+
This is especially useful on the commandline, but it is also
|
1353
|
+
useful to aggregate it together in different ruby files of
|
1354
|
+
this project, and present a "unified" API for this topic.
|
1355
|
+
|
1356
|
+
Note that since as of 09.11.2019 (9th of November), the number of
|
1357
|
+
available exam-topics as part of this project are calculated
|
1358
|
+
automatically. Prior to that a constant was used that was
|
1359
|
+
hand-counted manually by me, which was too tedious and error-prone -
|
1360
|
+
so the new approach should work better for more exam topics in
|
1361
|
+
the future.
|
1362
|
+
|
1363
|
+
## Studium.find_corresponding_exam_title
|
1364
|
+
|
1365
|
+
The method <b>Studium.find_corresponding_exam_title()</b> can be used
|
1366
|
+
to return the full, spelled out name of the exam topic at hand.
|
1367
|
+
|
1368
|
+
Let's showcase two examples next - these may explain what this method
|
1369
|
+
does more succinctly so:
|
1370
|
+
|
1371
|
+
title = Studium.find_corresponding_exam_title('technische_grundlagen_der_informatik') # => "Technische Grundlagen der Informatik"
|
1372
|
+
title = Studium.find_corresponding_exam_title('mphysio') # => "Mikrobielle Physiologie"
|
1373
|
+
|
1374
|
+
As can be seen, a short input, such as **mphysio**, will be translated
|
1375
|
+
into **Mikrobielle Physiologie** properly. I needed this in order
|
1376
|
+
to show the exam topic at hand; showing **mphysio** was not as
|
1377
|
+
useful as showing **Mikrobielle Physiologie** instead (which,
|
1378
|
+
by the way, is german for **microbial physiology**, that is
|
1379
|
+
metabolic pathways used by microorganisms).
|
1380
|
+
|
1381
|
+
## Studium::Exams::PushSolvedQuestionsOnTop
|
1382
|
+
|
1383
|
+
**class Studium::Exams::PushSolvedQuestionsOnTop** has a very simple
|
1384
|
+
objective: it will move all lines ending with ' []' to the top of
|
1385
|
+
a given file, if at the least one ' []' is encountered in that
|
1386
|
+
file. Note that "top of the given file" specifically excludes
|
1387
|
+
comments, that is lines starting with **#** in that file, and the
|
1388
|
+
first line after that '#' comment, which is just a newline for
|
1389
|
+
readability reasons usually.
|
1390
|
+
|
1391
|
+
The idea behind this class is really just to be able to quickly
|
1392
|
+
reshuffle all solved questions towards the top of the file;
|
1393
|
+
the unsolved questions will then be at the bottom of the file.
|
1394
|
+
|
1395
|
+
I needed this functionality because it allows me to quickly
|
1396
|
+
re-structure existing question-answers, into different
|
1397
|
+
topics/themes.
|
1398
|
+
|
1399
|
+
On my home system, I aliases it to <b>ontop</b> simply.
|
1400
|
+
|
1401
|
+
## Display the upcoming exams, via the timetable
|
1402
|
+
|
1403
|
+
You can show the list of <b>upcoming exams</b> via:
|
1404
|
+
|
1405
|
+
studium --timetable
|
1406
|
+
|
1407
|
+
Note that this makes use of the information stored in the file called
|
1408
|
+
<b>lecture_information.yml</b>, which has to be maintained by someone.
|
1409
|
+
In this case, I am still maintaining the dataset stored in that
|
1410
|
+
file (in the year **2019**) - but this may not be the case at a later
|
1411
|
+
time, so ideally someone else should be able to maintain that file,
|
1412
|
+
or just anyone. I will add sufficient documentation to explain what
|
1413
|
+
has to be done, in order to maintain that single file.
|
1414
|
+
|
1415
|
+
At any rate, the class that is responsible for interpreting the dataset
|
1416
|
+
stored in that .yml file, is **class Studium::Exams::UpcomingImportantExams**.
|
1417
|
+
|
1418
|
+
This is the very same class that is invoked by issuing
|
1419
|
+
<b>studium --timetable</b>.
|
1420
|
+
|
1421
|
+
The exam dates should ideally follow the **dd.mm.yyyy notation**,
|
1422
|
+
that is <b>day.month.year</b>.
|
1423
|
+
|
1424
|
+
An example will be given next. Say that you have a course called
|
1425
|
+
<b>Physics for Engineers</b>. Two exams for this course are upcoming,
|
1426
|
+
which you may wish to **register** in the above-mentioned yaml
|
1427
|
+
file, like in such a way:
|
1428
|
+
|
1429
|
+
"Physics for Engineers":
|
1430
|
+
- "02.02.2018"
|
1431
|
+
- "02.03.2018"
|
1432
|
+
|
1433
|
+
The above means that the next exam for the course "**Physics for
|
1434
|
+
Engineers**" will occur at the beginning of february; and then
|
1435
|
+
the next exam will be at the beginning of march, and so
|
1436
|
+
forth. You should sort this by date.
|
1437
|
+
|
1438
|
+
In the .yml file, the exam-related entries are called
|
1439
|
+
<b>exams:</b> and should denote an **Array**.
|
1440
|
+
|
1441
|
+
Once the exam has been registered like that,
|
1442
|
+
**class Studium::Exams::UpcomingImportantExams**
|
1443
|
+
will make use of the information. That's about it for
|
1444
|
+
that class. :)
|
1445
|
+
|
1446
|
+
## Showing upcoming exams
|
1447
|
+
|
1448
|
+
**class Studium::ShowUpcomingExams.new** can show **upcoming exams**,
|
1449
|
+
on the commandline.
|
1450
|
+
|
1451
|
+
The **first input argument** should be a number, e. g. 10, which
|
1452
|
+
means that the first 10 upcoming exams will be shown. For the
|
1453
|
+
next 20 exams, it would be **d20**.
|
1454
|
+
|
1455
|
+
Note that this **depends on aliases** called "**pwdstud1**" or
|
1456
|
+
"**pwdstud2**". These have to exist in a yaml file (on my system
|
1457
|
+
this is the yaml file named **cd_aliases.yml**). The display is
|
1458
|
+
on the commandline but in principle, a **GUI** could be used as
|
1459
|
+
well for this task.
|
1460
|
+
|
1461
|
+
Do note that when this class is invoked, it will additionally store
|
1462
|
+
the result into a file called, e. g. **d20.md** or **d10.md**. This
|
1463
|
+
would allow you to upload that file if you want to. I needed that
|
1464
|
+
functionality because I wanted to display the upcoming exams
|
1465
|
+
somewhere else other than on my machine, for when I am not at home.
|
1466
|
+
|
1467
|
+
Note that there does exist another class, which can show upcoming
|
1468
|
+
exams, via a **.html** file. This class is called
|
1469
|
+
<b>Studium::Exams::UpcomingImportantExams</b>.
|
1470
|
+
|
1471
|
+
You can invoke class <b>Studium::Exams::UpcomingImportantExams</b>
|
1472
|
+
from the commandline by issuing something like the following:
|
1473
|
+
|
1474
|
+
studium --upcoming-exams
|
1475
|
+
|
1476
|
+
The display will be a HTML table essentially. In order for this
|
1477
|
+
to work, the file **lecture_information.yml** must contain the
|
1478
|
+
information for these upcoming exams - it is the only file
|
1479
|
+
that you may have to update, though. (In theory code could
|
1480
|
+
be added to automatically check for new exams, but this
|
1481
|
+
requires more code to be written. I am not sure if I will
|
1482
|
+
add this, simply due to time constraints alone.)
|
1483
|
+
|
1484
|
+
You can pass in some other commands to the file from the
|
1485
|
+
commandline, such as **--do-not-exit** - see the **--help
|
1486
|
+
option** for more information pertaining to class
|
1487
|
+
<b>Studium::Exams::UpcomingImportantExams</b>.
|
1488
|
+
|
1489
|
+
## Graphviz: generating module dependencies
|
1490
|
+
|
1491
|
+
Since as of December 2019 it is possible to generate a module
|
1492
|
+
dependency image (as a .png file). This depends on the project
|
1493
|
+
called **ImageParadise**, and on the program called graphviz.
|
1494
|
+
|
1495
|
+
The code works, but it is not really optimized or very flexible.
|
1496
|
+
Consider it more as a proof-of-concept for the time being -
|
1497
|
+
perhaps in the future this may be extended.
|
1498
|
+
|
1499
|
+
(Note that most of the code for this can be found in the
|
1500
|
+
image_paradise gem; the studium gem only generates the
|
1501
|
+
Hash that is passed into image_paradise, and it is
|
1502
|
+
then the responsibility of image_paradise to generate
|
1503
|
+
the image file at hand.)
|
1504
|
+
|
1505
|
+
## Evaluating the progress in different curricula
|
1506
|
+
|
1507
|
+
You can evaluate your progress in different curricula via class
|
1508
|
+
<b>Studium::CurriculumComparer</b>. This class resides within the
|
1509
|
+
<b>statistics/</b> subdirectory of this gem.
|
1510
|
+
|
1511
|
+
In order for this class to work properly, all your successfully completed
|
1512
|
+
lectures have to be registered in the file <b>lecture_information.yml</b>
|
1513
|
+
prior to using that class. (Thus, you need to use your own dataset,
|
1514
|
+
but this is the only sensible thing to do; it would not make a lot of
|
1515
|
+
sense for you to use my dataset, since that makes no sense for
|
1516
|
+
**your** particular progress in your own studies. People will have
|
1517
|
+
to maintain their own dataset here.)
|
1518
|
+
|
1519
|
+
The class will then output which curricula have the highest amount
|
1520
|
+
of successfully completed ECTS points, sorted first. That way you
|
1521
|
+
can assess how far you have gotten in this or that curriculum so
|
1522
|
+
far.
|
1523
|
+
|
1524
|
+
## Deprecations within the Studium gem
|
1525
|
+
|
1526
|
+
This subsection may eventually contain deprecations within the
|
1527
|
+
Studium gem itself.
|
1528
|
+
|
1529
|
+
- class Studium::Exams::ShowExamThemes was deprecated on
|
1530
|
+
01.06.2020; most of its functionality was integrated into
|
1531
|
+
class Studium::Exams::ShowThemes. The new code is better
|
1532
|
+
than the old code, in my opinion. Less confusing.
|
1533
|
+
|
1534
|
+
The file **participating_in_these_courses.yml** was removed.
|
1535
|
+
Users now have to designate whether they participate in a
|
1536
|
+
university course with the corresponding LV-entry in the
|
1537
|
+
file **lecture_information.yml**.
|
1538
|
+
|
1539
|
+
The two constants **STORE_LAST_QUESTION_ASKED_WHERE** and
|
1540
|
+
**FILE_LAST_QUESTION_ASKED** were removed. Use the toplevel-method
|
1541
|
+
**Studium.file_last_question_asked?** instead if you want
|
1542
|
+
to find out where the last exam question is stored.
|
1543
|
+
|
1544
|
+
## Sinatra interface
|
1545
|
+
|
1546
|
+
The Studium project has a small sinatra interface, which can
|
1547
|
+
be started like this from the commandline:
|
1548
|
+
|
1549
|
+
studium --sinatra
|
1550
|
+
|
1551
|
+
(If this fails, try to reload again. On my system I have
|
1552
|
+
tied this to open it in the browser the moment sinatra
|
1553
|
+
is started, and this takes perhaps two or there seconds.)
|
1554
|
+
|
1555
|
+
Note that the sinatra-interface is fairly minimal, but it
|
1556
|
+
can be used to display different curricula. Expect this
|
1557
|
+
to be improved in the long run (past **June 2020**).
|
1558
|
+
|
1559
|
+
## Determining the name of a curriculum
|
1560
|
+
|
1561
|
+
If you have a use case for determining (and returning) the
|
1562
|
+
name of a curriculum, you can do this:
|
1563
|
+
|
1564
|
+
require 'studium/toplevel_methods/name_of_this_curriculum.rb'
|
1565
|
+
|
1566
|
+
Studium.name_of_this_curriculum
|
1567
|
+
Studium.name_of_this_curriculum(:indi2)
|
1568
|
+
Studium.name_of_this_curriculum(:tu_wien_chem) # => "Technische Chemie"
|
1569
|
+
|
1570
|
+
## class Studium::Exams::UpcomingExams
|
1571
|
+
|
1572
|
+
class Studium::Exams::UpcomingExams can report which exams are
|
1573
|
+
upcoming, via a HTML table.
|
1574
|
+
|
1575
|
+
## class Studium::Calendar
|
1576
|
+
|
1577
|
+
class **Studium::Calendar** attempts to display which courses are
|
1578
|
+
upcoming, so that you can plan ahead. It currently works only on
|
1579
|
+
the commandline, but in the future ruby-gtk bindings and a
|
1580
|
+
sinatra-web-interface may be added - we'll see.
|
1581
|
+
|
1582
|
+
The main dataset for this class is derived from the file
|
1583
|
+
called **participating_in_these_courses.yml**. The key
|
1584
|
+
that is listed there will become the full name.
|
1585
|
+
|
1586
|
+
The class was added in September 2020, so expect things
|
1587
|
+
to not work pefectly well for the time being - it will
|
1588
|
+
be improved upon at a later time.
|
1589
|
+
|
1590
|
+
## Showing all STEOP lectures of a curriculum
|
1591
|
+
|
1592
|
+
You can show all STEOP lectures that are in a curriculum.
|
1593
|
+
|
1594
|
+
Issue something like the following on the commandline:
|
1595
|
+
|
1596
|
+
steop_lectures --curriculum1
|
1597
|
+
steop_lectures --curriculum2 # number-input should work
|
1598
|
+
steop_lectures --ktww
|
1599
|
+
steop_lectures --lbt # Bachelor Biotech-Curriculum at the BOKU
|
1600
|
+
steop_lectures --AW # as should abbreviations; AW is "Agrarwissenschaften"
|
1601
|
+
steop_lectures_in_this_curriculum --ktww
|
1602
|
+
|
1603
|
+
Where **steop_lectures** is an alias to where class
|
1604
|
+
**Studium::SteopLecturesInThisCurriculum** resides - usually
|
1605
|
+
in the file **studium/steop/steop_lectures_in_this_curriculum.rb**.
|
1606
|
+
|
1607
|
+
If you want to show all steop-lectures in the current semester,
|
1608
|
+
consider using <b>Studium::SteopLvaDates.new</b>.
|
1609
|
+
|
1610
|
+
## Semesterplaner - planning a given semester (half-year) at a university
|
1611
|
+
|
1612
|
+
There is a class that may try to plan ahead for a given semester
|
1613
|
+
at a university. This class is not very flexible and such but
|
1614
|
+
the code could be improved.
|
1615
|
+
|
1616
|
+
See:
|
1617
|
+
|
1618
|
+
require 'studium/utility_scripts/semesterplaner.rb'
|
1619
|
+
Studium::Semesterplaner.new
|
1620
|
+
|
1621
|
+
## Display exam statistics
|
1622
|
+
|
1623
|
+
To show the exam statistics, try:
|
1624
|
+
|
1625
|
+
Studium.show_exam_statistics
|
1626
|
+
|
1627
|
+
## class Studium::ShowLvaDatesOfThisLecture
|
1628
|
+
|
1629
|
+
If you need to show the **LVA dates** of a given lecture at hand, on
|
1630
|
+
the <b>commandline</b>, then you may want to use <b>class
|
1631
|
+
Studium::ShowLvaDatesOfThisLecture</b>, defined in the file
|
1632
|
+
<b>studium/utility_scripts/show_lva_dates_of_this_lecture.rb</b>.
|
1633
|
+
|
1634
|
+
The usage for this class is quite simple - pass in the name of the
|
1635
|
+
lecture that you are interested in, such as "Primatologie".
|
1636
|
+
|
1637
|
+
If you want to get the most accurate information, then you should
|
1638
|
+
ideally also pass in the lecture ID; such as in the above example
|
1639
|
+
with "Primatologie", the input string should be in the form of:
|
1640
|
+
|
1641
|
+
"300227 Primatologie"
|
1642
|
+
|
1643
|
+
We call the "300227 Primatologie" variant as the <b>full
|
1644
|
+
input</b> and the variant with "Primatologie" alone as
|
1645
|
+
<b>partial input</b>. If only a partial input is provided,
|
1646
|
+
then the script will try to be <b>greedy</b> and find as
|
1647
|
+
many relevant entries as possible. This can be used as a
|
1648
|
+
feature too.
|
1649
|
+
|
1650
|
+
For example, consider that <b>show_lva_dates_of_this_lecture</b>
|
1651
|
+
is an alias to the above .rb file, then the following
|
1652
|
+
commandline use:
|
1653
|
+
|
1654
|
+
show_lva_dates_of_this_lecture Geneti
|
1655
|
+
|
1656
|
+
would show all lectures that have the tag "Geneti"
|
1657
|
+
included.
|
1658
|
+
|
1659
|
+
Note that you do not necessarily need an alias such as
|
1660
|
+
<b>show_lva_dates_of_this_lecture</b>; you can also invoke
|
1661
|
+
it from the commandline, as the following example shows:
|
1662
|
+
|
1663
|
+
studium --show-lva-dates-of-this-lecture=Primatologie
|
1664
|
+
studium --show-lva-dates-of-this-lecture="300227 Primatologie"
|
1665
|
+
|
1666
|
+
To use it in ruby code, try something like this:
|
1667
|
+
|
1668
|
+
require 'studium/utility_scripts/show_lva_dates_of_this_lecture.rb'
|
1669
|
+
result = Studium::ShowLvaDatesOfThisLecture.new("802300 Biological nanosciences and nanotechnology (in Eng.)")
|
1670
|
+
|
1671
|
+
## Expanding time ranges
|
1672
|
+
|
1673
|
+
Consider the situation where a student participates in a lecture
|
1674
|
+
requiring practical work time, such as by being active in a
|
1675
|
+
laboratory, with a time schedule requiring the students to
|
1676
|
+
begin early morning, and work until the late evening, over a
|
1677
|
+
time period of three weeks. (This is just an example to illustrate
|
1678
|
+
this subsection here; the *use case* is explained.)
|
1679
|
+
|
1680
|
+
You may see that the school/university displays the specific dates
|
1681
|
+
online via something like:
|
1682
|
+
|
1683
|
+
15.10. - 2.11.2020,
|
1684
|
+
|
1685
|
+
**Exactly** like this (this is actually a copy/pasted "real-world"
|
1686
|
+
example, including the trailing ',').
|
1687
|
+
|
1688
|
+
What does the above mean? Well, it means that the course will
|
1689
|
+
**begin** at the 15th of october, in the year 2020 (this is
|
1690
|
+
the dd.mm.yyyy notation which is in general used in europe).
|
1691
|
+
|
1692
|
+
The **-** in between means "up until" and the end date is
|
1693
|
+
specified to be at the second of november, in 2020.
|
1694
|
+
|
1695
|
+
Since I needed to quickly convert such short, one-line
|
1696
|
+
dates of a given course into a specific time for use in a
|
1697
|
+
**calendar-like application**, I needed a class that can output
|
1698
|
+
an Array of dates where this course will be held. So, class
|
1699
|
+
<b>Studium::ExpandTimeRange</b> was created to tackle this
|
1700
|
+
problem.
|
1701
|
+
|
1702
|
+
This class will accept such odd input as the last example, and
|
1703
|
+
then output an Array that can be used in a yaml file, of the specific
|
1704
|
+
dates, weekend-names associated with that day and the time. This
|
1705
|
+
then allows me to quickly copy/paste this into the corresponding
|
1706
|
+
yaml file. (I needed to have this expanded to every day because
|
1707
|
+
I also visually have to look at that yaml file. For this, it
|
1708
|
+
does help to have every day listed as-is, rather than specify
|
1709
|
+
a range such as **02.11-04.12**.)
|
1710
|
+
|
1711
|
+
Internally you can also use the following toplevel-method:
|
1712
|
+
|
1713
|
+
Studium.expand_time_range()
|
1714
|
+
Studium.expander()
|
1715
|
+
|
1716
|
+
Use whichever variant you prefer - the last method is quite short
|
1717
|
+
though, so you can use it like this:
|
1718
|
+
|
1719
|
+
Studium.expander('15.10. - 2.11.2018')
|
1720
|
+
|
1721
|
+
This also works over the **commandline**, of course:
|
1722
|
+
|
1723
|
+
studium --expand-time-range="15.10. - 2.11.2018,"
|
1724
|
+
studium --expander="15.10.-2.11.2018"
|
1725
|
+
|
1726
|
+
## Querying whether a student is registered for a particular exam
|
1727
|
+
|
1728
|
+
To query and thus determine whether you are registered for a
|
1729
|
+
particular exam, use this method:
|
1730
|
+
|
1731
|
+
Studium.registered_for_this_exam?
|
1732
|
+
Studium.registered_for_this_exam? "892104 Physik (LBT)"
|
1733
|
+
|
1734
|
+
Note that in order for this to work, the information has
|
1735
|
+
to be registered for that particular course, e. g. as
|
1736
|
+
**registered** - that is typically found right above the
|
1737
|
+
**exams** setting, if it exists.
|
1738
|
+
|
1739
|
+
## class Studium::GenerateSpreadsheet
|
1740
|
+
|
1741
|
+
The idea for class Studium::GenerateSpreadsheet was to
|
1742
|
+
generate a spreadsheet (LibreOffice excel file) for
|
1743
|
+
individual curricula automatically. This works partially
|
1744
|
+
in the sense that the generated file is correct, but
|
1745
|
+
its visual looks are not necessarily ... awesome. If
|
1746
|
+
you need to use it, I recommend to use this only as
|
1747
|
+
a blueprint, and make enhancement to the generated
|
1748
|
+
file manually.
|
1749
|
+
|
1750
|
+
## Reporting all lectures that match to a specific lecture type
|
1751
|
+
|
1752
|
+
If you need to find out all registered lectures that match
|
1753
|
+
a particular type, such as 'VO', or 'UE' or 'VO+SE', then you
|
1754
|
+
can use the following toplevel-method:
|
1755
|
+
|
1756
|
+
Studium.report_all_lectures_matching_this_lecture_type('VO+SE')
|
1757
|
+
|
1758
|
+
The latter was the primary reason why this method has been
|
1759
|
+
added; I needed to find out all lecture types that are
|
1760
|
+
of combined VO + SE style ("VO" for "Vorlesung", "SE"
|
1761
|
+
for "Seminar").
|
1762
|
+
|
1763
|
+
## Report how many ECTS were solved per university
|
1764
|
+
|
1765
|
+
This can be done via:
|
1766
|
+
|
1767
|
+
Studium::EctsPerUniversity.new
|
1768
|
+
|
1769
|
+
Or via the **commandline**, through <b>bin/studium</b>:
|
1770
|
+
|
1771
|
+
studium --ects-per-university
|
1772
|
+
|
1773
|
+
## Showing the weekly lectures
|
1774
|
+
|
1775
|
+
In order to show the weekly lectures, you can use **class WeekParser**.
|
1776
|
+
|
1777
|
+
## class Studium::UpcomingMandatoryPresenceCourses.new
|
1778
|
+
|
1779
|
+
class Studium::UpcomingMandatoryPresenceCourses.new can be
|
1780
|
+
used to show the upcoming courses that require your physical
|
1781
|
+
presence. By default this class will "peek ahead" 40 days
|
1782
|
+
into the future; this can be modified via the method
|
1783
|
+
**.set_n_days_into_the_future()**.
|
1784
|
+
|
1785
|
+
You can also invoke this on the commandline via:
|
1786
|
+
|
1787
|
+
studium --mandatory
|
1788
|
+
|
1789
|
+
## Working with a curriculum
|
1790
|
+
|
1791
|
+
From the ruby side, you can do this:
|
1792
|
+
|
1793
|
+
require 'studium'
|
1794
|
+
|
1795
|
+
this_curriculum = Studium::Curriculum.new(:bachelor_vektoren)
|
1796
|
+
|
1797
|
+
## Studium.backup_this_exam_file
|
1798
|
+
|
1799
|
+
The method **Studium.backup_this_exam_file()** may be used from
|
1800
|
+
various classes, but most importantly it is used by
|
1801
|
+
**class AskExamQuestion**. The idea here is to first back up
|
1802
|
+
the **old** exam question file, before making any changes. That
|
1803
|
+
way you can restore to the prior file, if you ever need to.
|
1804
|
+
|
1805
|
+
## Marking all exam questions of a given topic to solved
|
1806
|
+
|
1807
|
+
If you want to mark all questions of a particular topic to
|
1808
|
+
"solved" then you can try this:
|
1809
|
+
|
1810
|
+
qa agrarmarkt --ALL_SOLVED
|
1811
|
+
qa agrarmarkt --all-solved
|
1812
|
+
|
1813
|
+
This will solve all topics from agrarmarkt to **solved**.
|
1814
|
+
|
1815
|
+
Internally this will ensure that each line has a trailing
|
1816
|
+
**[]**.
|
1817
|
+
|
1818
|
+
## Colours
|
1819
|
+
|
1820
|
+
The **colours** within the Studium project are handled in two main ways:
|
1821
|
+
|
1822
|
+
(1) By an external gem called colours
|
1823
|
+
|
1824
|
+
(2) Internally in most classes of this project via the @use_colours instance variable.
|
1825
|
+
|
1826
|
+
In other words, if the toplevel instance variable **@use_colours** is set
|
1827
|
+
to **false** then the Studium project/namespace will not use colours at
|
1828
|
+
all. That way you can **disable colours** for the whole project. This may
|
1829
|
+
be useful if you use the project in sinatra or rails and so forth.
|
1830
|
+
|
1831
|
+
In ruby code you could invoke the following method in order to achieve
|
1832
|
+
this:
|
1833
|
+
|
1834
|
+
Studium.disable_colours
|
1835
|
+
|
1836
|
+
By default, on the **commandline**, for exam questions and exam answers
|
1837
|
+
to said question, colours can be defined by the user, through the file
|
1838
|
+
called <b>studium/yaml/custom_colours.yml</b>.
|
1839
|
+
|
1840
|
+
That file has ***keys*** such as <b>colour_for_answers</b> and
|
1841
|
+
<b>colour_for_answers</b>, which denotes the colour to be used for
|
1842
|
+
when a question is asked and an answer to that question is revealed,
|
1843
|
+
on the commandline.
|
1844
|
+
|
1845
|
+
Currently this defaults to <b>olivedrab</b> for exam-questions and
|
1846
|
+
<b>lightslategray</b> for exam-answers, but you can use any other
|
1847
|
+
colour code here if you would like to. These HTML names are the
|
1848
|
+
preferred variants; if you need a link to these names, you could
|
1849
|
+
use this one here https://www.w3schools.com/colors/colors_hex.asp.
|
1850
|
+
|
1851
|
+
So, for example, that yaml file will have these entries:
|
1852
|
+
|
1853
|
+
colour_for_questions: olivedrab
|
1854
|
+
colour_for_answers: lightslategray
|
1855
|
+
|
1856
|
+
You can also change these colours through the commandline,
|
1857
|
+
as the next examples will demonstrate.
|
1858
|
+
|
1859
|
+
Examples:
|
1860
|
+
|
1861
|
+
studium --use-this-colour-for-exam-answers=slateblue
|
1862
|
+
studium --use-this-colour-for-exam-questions=grey
|
1863
|
+
|
1864
|
+
Do note that you can "style" exam questions and exam
|
1865
|
+
answers in various ways. For example, if you use "" quotes,
|
1866
|
+
then another colour will be used (this is no longer the
|
1867
|
+
case as of October 2020, though; you need to use HTML
|
1868
|
+
names instead, or special tags such as <one>).
|
1869
|
+
|
1870
|
+
If you use a tag such as <u> and </u> (a html pseudo-tag, u meaning
|
1871
|
+
**underline**), then the word will be underlined. You can also
|
1872
|
+
add HTML colours, such as <slateblue> this will be in
|
1873
|
+
slateblue colour. The latter variant may become shorter in the
|
1874
|
+
future, such as <slateblue >foo</> or something
|
1875
|
+
like that - but for now, you have to use the name of the HTML
|
1876
|
+
colour both in the opening and in the closing tag.
|
1877
|
+
|
1878
|
+
## class Studium::Exams::ShowUpcomingExams
|
1879
|
+
|
1880
|
+
The fairly useful **class ShowUpcomingExams** will display **the next n
|
1881
|
+
upcoming exams**, where n should be a number from 3-20, simply as that
|
1882
|
+
is more convenient to digest and read on the commandline. There are also
|
1883
|
+
files such as d10 or d20 in the **bin/** subdirectory of this gem, which
|
1884
|
+
defaults to e. g. 10 or 20 upcoming exams. That way you can, for example,
|
1885
|
+
type d100 and the next 100 upcoming exams are shown (I never had such
|
1886
|
+
a high number; the 100 here simply stands, sort of, for "show me all
|
1887
|
+
upcoming exams".)
|
1888
|
+
|
1889
|
+
Don't forget to keep the "register:" entry in the lecture_information.yml
|
1890
|
+
file, to indicate which exams are upcoming. In the past a separate
|
1891
|
+
file called **exams.yml** was used, but since some years this information
|
1892
|
+
is all unified and presented via the file called **lecture_information.yml**.
|
1893
|
+
|
1894
|
+
If you want to designate another file or location, have a look
|
1895
|
+
at the file **file_constants.rb**. You can also invoke this
|
1896
|
+
method to set another file position:
|
1897
|
+
|
1898
|
+
Studium.set_file_exams()
|
1899
|
+
|
1900
|
+
Simply pass the **location** of your exams-file, which must be
|
1901
|
+
a yaml file, into that method.
|
1902
|
+
|
1903
|
+
If you simply need the dataset of upcoming exams, you can use
|
1904
|
+
the following API for this:
|
1905
|
+
|
1906
|
+
require 'studium'
|
1907
|
+
dataset = Studium::ShowUpcomingExams.return_all_registered_upcoming_exams
|
1908
|
+
|
1909
|
+
## GUI - Graphical User Interface
|
1910
|
+
|
1911
|
+
The **studium gem** comes with a few GUI bindings, primarily based
|
1912
|
+
on those bindings available to ruby. Although using java is an
|
1913
|
+
option - and then using **swing** - at present no effort is made
|
1914
|
+
to add a GUI in java or jruby.
|
1915
|
+
|
1916
|
+
The current focus in this project, in regards to graphical user
|
1917
|
+
interfaces (in the year **2021**) is on GTK, in particular via the
|
1918
|
+
ruby-gtk3 bindings, which in turn depend on gobject-introspection.
|
1919
|
+
|
1920
|
+
Since as of <b>July 2022</b> the older ruby-gtk2 bindings were
|
1921
|
+
removed. The ruby-gtk3 bindings were of a much higher quality
|
1922
|
+
anyway and it is a waste of time to maintain ruby-gtk2 code.
|
1923
|
+
Note that my other project called <b>gtk_paradise</b> will
|
1924
|
+
continue to support ruby-gtk2 - I just don't think ruby-gtk2
|
1925
|
+
will be useful for the studium gem anymore past <b>July 2022</b>.
|
1926
|
+
|
1927
|
+
Further GUI elements may be added in the future, such as
|
1928
|
+
more sinatra-specific code, more .cgi files, perhaps rails
|
1929
|
+
as well, and libui. The latter works on windows
|
1930
|
+
out-of-the-box if you do "gem install libui", which
|
1931
|
+
is a huge plus.
|
1932
|
+
|
1933
|
+
If you want to make use of the GTK bindings then you currently need
|
1934
|
+
the **gtk_paradise** gem, so make sure to install it first. Prior to that
|
1935
|
+
you will also need to have the necessary gtk-files, headers and what not.
|
1936
|
+
Your distribution (if you use Linux) may have packaged these for you,
|
1937
|
+
so research this a little how to obtain all necessary files. I myself
|
1938
|
+
tend to compile from source, so I don't really know the names of
|
1939
|
+
the packages different distributions use here.
|
1940
|
+
|
1941
|
+
The **main GUI widget** for **asking exam questions** currently
|
1942
|
+
(at the least past **February 2021**) looks like this:
|
1943
|
+
|
1944
|
+
<img src="https://i.imgur.com/LOmMhht.png" style="margin: 1em; margin-left: 3em">
|
1945
|
+
|
1946
|
+
In **September 2021** this was enhanced a bit and should look slightly
|
1947
|
+
better now:
|
1948
|
+
|
1949
|
+
<img src="https://i.imgur.com/zpgUCVR.png" style="margin: 1em; margin-left: 3em">
|
1950
|
+
|
1951
|
+
(Don't mind the answer in the above screenshot being wrong; the lower
|
1952
|
+
input-field is just for giving an answer before hitting the reveal
|
1953
|
+
button to check whether you gave the correct answer. It's a training
|
1954
|
+
system, so of course wrong answers may be given. The above image is
|
1955
|
+
mostly about showcasing the **functionality** as such.)
|
1956
|
+
|
1957
|
+
Note that a **.css** file covers most of the display settings, so users of
|
1958
|
+
the studium gem could, in principle, **adjust it to their liking via
|
1959
|
+
a CSS file**. I am willing to change the widget composition and
|
1960
|
+
functionality as-is, and offer ad-hoc loading of .css files if this
|
1961
|
+
is wanted, but most of the time I just use the commandline variant
|
1962
|
+
only, anyway.
|
1963
|
+
|
1964
|
+
Since as of September 2021 a variation exists, called FastAskExamQuestion.
|
1965
|
+
The old GUI was becoming slow, for some awkward reason, so I simplified
|
1966
|
+
it, removed some features - it should now be more responsive. It may
|
1967
|
+
not be as convenient to use, but if you only want a simple GUI for
|
1968
|
+
exam-questions then consider making use of FastAskExamQuestion
|
1969
|
+
rather than AskExamQuestion.
|
1970
|
+
|
1971
|
+
It now looks like this:
|
1972
|
+
|
1973
|
+
<img src="https://i.imgur.com/oPTItPy.png" style="margin: 1em; margin-left: 2em">
|
1974
|
+
|
1975
|
+
It now has fewer features, but I think it looks better organized now, and most
|
1976
|
+
importantly it is faster. Perhaps the issue was unrelated to that widget; either
|
1977
|
+
way this new variant will probably retained in the long run.
|
1978
|
+
|
1979
|
+
The current (August 2021) variant of libui looks like this:
|
1980
|
+
|
1981
|
+
<img src="https://i.imgur.com/ZLsymdN.png" style="margin-left: 1em">
|
1982
|
+
|
1983
|
+
Yes, that looks like crap and it is incomplete - but the big win is that this
|
1984
|
+
will also work on windows, out of the box, without any further ado. The idea
|
1985
|
+
here is that windows users can now work via a GUI tool past this point.
|
1986
|
+
**ruby-gtk3** works very well on Linux, but I could not get GTK to
|
1987
|
+
work on windows, despite the so-called 'official guide' for msys2. Thanks
|
1988
|
+
to libui it is no longer necessary to wait until I get gtk to work on
|
1989
|
+
windows - it now works **as-is**.
|
1990
|
+
|
1991
|
+
You may still want to distribute - or use - an **.exe** file on
|
1992
|
+
windows. This is possible if you use the **ocra** gem.
|
1993
|
+
|
1994
|
+
If you are on windows, then run **bin/studium** like this:
|
1995
|
+
|
1996
|
+
ruby studium --create-executable
|
1997
|
+
|
1998
|
+
This should build an .exe file that can be started.
|
1999
|
+
|
2000
|
+
(That .exe currently, in August 2021, does not work perfectly
|
2001
|
+
well. I have to fix some related ruby code first, but starting
|
2002
|
+
the libui-widget directly via **ruby** works fine - I tested
|
2003
|
+
that on windows too.)
|
2004
|
+
|
2005
|
+
## class Studium::DisplayLectureUrl
|
2006
|
+
|
2007
|
+
This class can display lectures and their associated remote URL
|
2008
|
+
(the homepage) via the commandline.
|
2009
|
+
|
2010
|
+
Basic usage example:
|
2011
|
+
|
2012
|
+
require 'studium/utility_scripts/display_lecture_url.rb'
|
2013
|
+
Studium::DisplayLectureUrl.new(ARGV)
|
2014
|
+
Studium::DisplayLectureUrl.new('--indi2')
|
2015
|
+
|
2016
|
+
This class can either output just one lecture's course
|
2017
|
+
URL, or operate in a batch-mode where all lectures of
|
2018
|
+
a curriculum are displayed.
|
2019
|
+
|
2020
|
+
## The toplevel-method Studium.filter_away_invalid_questions
|
2021
|
+
|
2022
|
+
The toplevel-method **Studium.filter_away_invalid_questions()**,
|
2023
|
+
defined in the file **studium/toplevel_methods/filter_away_invalid_questions.rb**,
|
2024
|
+
is used to filter away invalid questions.
|
2025
|
+
|
2026
|
+
This essentially removes any empty lines or lines starting with the
|
2027
|
+
**#** character, which is assumed to be a comment.
|
2028
|
+
|
2029
|
+
After this method has been invoked on a dataset, it is assumed
|
2030
|
+
that this dataset will contain only valid (legal) exam
|
2031
|
+
questions.
|
2032
|
+
|
2033
|
+
You can tap into the following method to determine the path to
|
2034
|
+
the exam topics:
|
2035
|
+
|
2036
|
+
Studium.path_to_the_exam_topics?
|
2037
|
+
|
2038
|
+
So you can then read in the exam-topic file, call
|
2039
|
+
the Studium.filter_away_invalid_questions() method,
|
2040
|
+
and then randomly select a remaining exam topic to
|
2041
|
+
ask.
|
2042
|
+
|
2043
|
+
To obtain a random exam topic, use this API:
|
2044
|
+
|
2045
|
+
Studium.random_exam_topic? # => "epigenetik"
|
2046
|
+
Studium.random_exam_topic? # => "abfall_als_ressource"
|
2047
|
+
Studium.random_exam_topic? # => "embryologie_und_entwicklung"
|
2048
|
+
|
2049
|
+
## Statistical information within the Studium project
|
2050
|
+
|
2051
|
+
The Studium project also allows for a few **statistical information**
|
2052
|
+
in regards to the project, e. g. such as how many exams were passed
|
2053
|
+
in this or that period of time. You can also show the curricula used
|
2054
|
+
for any given individual curriculum at hand.
|
2055
|
+
|
2056
|
+
The latter feature can be invoked such as is shown next:
|
2057
|
+
|
2058
|
+
studium --statistics
|
2059
|
+
|
2060
|
+
This will tap into <b>class Studium::DetermineCurricula</b>.
|
2061
|
+
|
2062
|
+
What about "how many exam questions can a human being solve
|
2063
|
+
per given day"? Well, this is a generic question really, and
|
2064
|
+
it will depend on the individual. Some people learn faster
|
2065
|
+
than others, for many reasons. The dataset I compiled for
|
2066
|
+
myself is not applicable to many other people - you'd need
|
2067
|
+
to do so consistently and study a whole cohort of people,
|
2068
|
+
in order to answer this question.
|
2069
|
+
|
2070
|
+
But if we ignore the cohort-situation, just for me, personally,
|
2071
|
+
I found a few interesting facts. In November 2021 the maximum
|
2072
|
+
exam-questions answered for me were **10.729**. In
|
2073
|
+
February of 2020 I reset that counter to 0, for various
|
2074
|
+
reasons. Then I resumed answering exam questions. In November
|
2075
|
+
2021 I broke 10.000 again, so the number of 10.729 is not
|
2076
|
+
a fluke - it's a real number for at the least my own situation.
|
2077
|
+
So, answering 10.000 exam questions may take me about a year
|
2078
|
+
and a half, give or take. (Remember that I did not necessarily
|
2079
|
+
answer the same exam questions again, so I may be above
|
2080
|
+
11.000 right now, most likely.)
|
2081
|
+
|
2082
|
+
So, if I estimate, in 18 months I answer 10.000 questions,
|
2083
|
+
and 18 months have roughly 18*30 540 days, then I can answer
|
2084
|
+
10_000 / 540.0 **18.5 exam questions per day**. Keep in mind
|
2085
|
+
that I did not answer exam questions on every day, and I wasn't
|
2086
|
+
really pushing this every day either, so this is more a relaxed
|
2087
|
+
approach. So a human being can very easily learn something
|
2088
|
+
new every day, with about 20 exam questions per day at minimum.
|
2089
|
+
(I consider myself average in this regard, so tons of people
|
2090
|
+
will have better numbers than these.)
|
2091
|
+
|
2092
|
+
This statistic may be fairly useless for others to know, but I
|
2093
|
+
find it quite interesting nonetheless. Imagine if I would have started
|
2094
|
+
with this when I was a little kid - my current knowledge would
|
2095
|
+
be significantly larger than what I have available right now.
|
2096
|
+
Whether the time investment pays off in the long run is hard
|
2097
|
+
to say - after all you also learn something new anyway, even
|
2098
|
+
without exam questions. Think about mechanical repair knowledge,
|
2099
|
+
which you can not easily obtain just from reading text; you need
|
2100
|
+
the physical practice too. But specifically for exam-related topics,
|
2101
|
+
where only theoretical knowledge is to be considered, this is
|
2102
|
+
quite helpful, in my opinion.
|
2103
|
+
|
2104
|
+
My next goal is to break 15.000 and then 20.000. Let's see
|
2105
|
+
how long this will take. :)
|
2106
|
+
|
2107
|
+
## class Studium::Exams::ExamQuestion
|
2108
|
+
|
2109
|
+
class **Studium::Exams::ExamQuestion** has been written in **January
|
2110
|
+
2022**. It replaced two older classes which formed the foundation of
|
2111
|
+
the "ask an exam-question" functionality.
|
2112
|
+
|
2113
|
+
The primary reason why it was rewritten was because there were
|
2114
|
+
several bugs in regards to coloured output on the commandline,
|
2115
|
+
via **ANSI escape sequences**. These bugs were fixed during
|
2116
|
+
the rewrite. \o/
|
2117
|
+
|
2118
|
+
The class, called from the commandline, may generate a question/answer
|
2119
|
+
output such as the following:
|
2120
|
+
|
2121
|
+
<img src="https://i.imgur.com/6D7KBHe.png" style="margin: 1em;">
|
2122
|
+
|
2123
|
+
This shows the question on top, and then the revealed answer
|
2124
|
+
below, via colours. The colours can be customized a little via
|
2125
|
+
a .yml file.
|
2126
|
+
|
2127
|
+
## class Studium::Exams::Solved
|
2128
|
+
|
2129
|
+
Since as of **January 2022**, class **Studium::Exams::Solved** will
|
2130
|
+
be more verbose if you call it from the commandline via:
|
2131
|
+
|
2132
|
+
solved --be-verbose
|
2133
|
+
|
2134
|
+
I needed this because there were some bugs that had to be
|
2135
|
+
removed, and it seemed more convenient to let this class
|
2136
|
+
respond to some user-given commands.
|
2137
|
+
|
2138
|
+
## Creating a SQL database
|
2139
|
+
|
2140
|
+
The exam-questions that are distributed by the studium gem can be
|
2141
|
+
turned into a **.sql database** (**SQL**).
|
2142
|
+
|
2143
|
+
A helper script exists to do this, at the file location
|
2144
|
+
**studium/database/create_database.rb**. If you run it
|
2145
|
+
a .sql file will be created, which is quite large - around
|
2146
|
+
8MB in size or more. This can then be read into a
|
2147
|
+
sqlite database.
|
2148
|
+
|
2149
|
+
Creating a new .sql database takes quite some time, though.
|
2150
|
+
Presently (in 2022) I don't have a better solution for this
|
2151
|
+
problem.
|
2152
|
+
|
2153
|
+
If you want to create it on your own host system, first invoke
|
2154
|
+
that .rb file, which is possible via the commandline via:
|
2155
|
+
|
2156
|
+
studium --create-database
|
2157
|
+
|
2158
|
+
Then a new .db file will be automatically created. But again,
|
2159
|
+
be warned, this takes quite some time.
|
2160
|
+
|
2161
|
+
## The file allowed_themes_for_exams.yml
|
2162
|
+
|
2163
|
+
The file <b>allowed_themes_for_exams.yml</b> lists the allowed themes
|
2164
|
+
for exams. For instance, a lecture that deals with Genetics and
|
2165
|
+
Cell Biology, may have as allowed themes at the least these two
|
2166
|
+
topics (e. g. **- genetics** and **- cell biology**).
|
2167
|
+
|
2168
|
+
The reason why this yaml file exists is so that we can use this
|
2169
|
+
to search for lectures that include these topics. So, in some
|
2170
|
+
ways, this is for the use case as a **meta-tagger**.
|
2171
|
+
|
2172
|
+
## The file curricula.yml
|
2173
|
+
|
2174
|
+
The file curricula.yml will keep all Curricula entries for
|
2175
|
+
curricula in **Austria**. This is mostly done so that we
|
2176
|
+
have these curricula registered, via number mapping to the
|
2177
|
+
corresponding name.
|
2178
|
+
|
2179
|
+
## Last saved into which file
|
2180
|
+
|
2181
|
+
Whenever you ask an exam-question, it is kept track into which
|
2182
|
+
file that exam-question will be stored. The toplevel API
|
2183
|
+
<b>Studium.last_saved_into_which_file?</b> can be used
|
2184
|
+
to query this.
|
2185
|
+
|
2186
|
+
It would then yield a path such as:
|
2187
|
+
|
2188
|
+
/home/x/programming/ruby/src/studium/lib/studium/exam_topics/basic_chemistry
|
2189
|
+
|
2190
|
+
## class Studium::SearchFor_nECTS
|
2191
|
+
|
2192
|
+
**class Studium::SearchFor_nECTS** can be used to show all lectures having the
|
2193
|
+
specified n ECTS credits.
|
2194
|
+
|
2195
|
+
So for example:
|
2196
|
+
|
2197
|
+
Studium::SearchFor_nECTS.new(1)
|
2198
|
+
|
2199
|
+
would show all lectures having **1.0 ECTS points**.
|
2200
|
+
|
2201
|
+
You can invoke this class from the commandline as well, of course. The name
|
2202
|
+
of the executable is **n_ECTS**, residing at **bin/n_ECTS**.
|
2203
|
+
|
2204
|
+
I aliased this executable to **nects** on my home system, and can then
|
2205
|
+
do the following as-is:
|
2206
|
+
|
2207
|
+
nects 1.0 --master --show-numbers
|
2208
|
+
|
2209
|
+
This would show all lectures belonging to a master-curriculum
|
2210
|
+
having 1.0 ECTS points. Additionally, the leading LVA ID numbers
|
2211
|
+
will be shown as well.
|
2212
|
+
|
2213
|
+
## Studium::Exams.report_nquestions_of
|
2214
|
+
|
2215
|
+
The method Studium::Exams.report_nquestions_of() can be used to quickly
|
2216
|
+
report how many exam questions are available in a particular exam
|
2217
|
+
topic. If you pass in an Array of exam-topics, such as 'bem1',
|
2218
|
+
'bem2', 'metabolism', then the method will report the total amount of
|
2219
|
+
exam-questions in all these exam topics combined. I use this to
|
2220
|
+
query "meta"-topics combined, such as biochemistry1, biochemistry2,
|
2221
|
+
and so forth.
|
2222
|
+
|
2223
|
+
## Studium::Statistics::TopStats
|
2224
|
+
|
2225
|
+
class **Studium::Statistics::TopStats** can be used to
|
2226
|
+
display the percentage value of questions answered in the
|
2227
|
+
registered exam topics. The purpose is to, simply and quickly,
|
2228
|
+
show the performance over the registered exam-topics in use.
|
2229
|
+
|
2230
|
+
Invocation example from ruby code:
|
2231
|
+
|
2232
|
+
Studium::Statistics::TopStats.new(ARGV)
|
2233
|
+
|
2234
|
+
The following small image shows how this may look, being
|
2235
|
+
applied onto the exam-dataset that I use normally:
|
2236
|
+
|
2237
|
+
<img src="https://i.imgur.com/rhOyyuF.png" style="margin: 1em; margin-left: 3em; border: 2px solid black">
|
2238
|
+
|
2239
|
+
## Studium.report_solved_topics
|
2240
|
+
|
2241
|
+
The solved topics can be quickly displayed if you use the
|
2242
|
+
following file and code:
|
2243
|
+
|
2244
|
+
require 'studium/toplevel_methods/report_solved_topics.rb'
|
2245
|
+
Studium.report_solved_topics
|
2246
|
+
|
2247
|
+
## class Studium::Exams::MandatoryContinuousAssessment
|
2248
|
+
|
2249
|
+
class <b>Studium::Exams::MandatoryContinuousAssessment</b> can
|
2250
|
+
be used to handle lectures that require mandatory attendance
|
2251
|
+
(in german "prüfungsimmanente Lehrveranstaltungen").
|
2252
|
+
|
2253
|
+
The section here does not include all options that this class
|
2254
|
+
is able to handle; instead, only a select subset will be shown
|
2255
|
+
and explained here.
|
2256
|
+
|
2257
|
+
If you want to show which mandatory courses may be upcoming,
|
2258
|
+
sorted on the assigned priority, then you can do this:
|
2259
|
+
|
2260
|
+
mandatory --upcoming
|
2261
|
+
|
2262
|
+
The command <b>mandatory</b> is an alias I use to
|
2263
|
+
the .rb file that holds
|
2264
|
+
<b>class Studium::Exams::MandatoryContinuousAssessment</b>.
|
2265
|
+
|
2266
|
+
You can also compare (some of) the registered curricula,
|
2267
|
+
by issuing:
|
2268
|
+
|
2269
|
+
mandatory --compare
|
2270
|
+
|
2271
|
+
This will output the amount of ECTS points stored in
|
2272
|
+
courses that require a mandatory attendance.
|
2273
|
+
|
2274
|
+
If you want to also see the individual lectures and courses
|
2275
|
+
that were used to determine all courses requiring mandatory
|
2276
|
+
presence, you can use the following commandline switch:
|
2277
|
+
|
2278
|
+
mandatory --compare-detail
|
2279
|
+
mandatory --compare-stats
|
2280
|
+
mandatory --details
|
2281
|
+
|
2282
|
+
On a side-note: if you wish to see some mandatory lectures,
|
2283
|
+
such as those that belong to the lecture type VO+SE, you
|
2284
|
+
can pass this as input to **bin/studium**, like so:
|
2285
|
+
|
2286
|
+
studium VO+SE
|
2287
|
+
|
2288
|
+
You can also query "which mandatory lectures are offered
|
2289
|
+
in the summer semester" and combine it with "which
|
2290
|
+
mandatory lectures are offered at the TU Vienna, via:
|
2291
|
+
|
2292
|
+
mandatory --tuwien --summer
|
2293
|
+
|
2294
|
+
Of course you need to have them registered first, such
|
2295
|
+
as in the file **lecture_information.yml**, if you wish
|
2296
|
+
to adapt it to your own universities. The default datset
|
2297
|
+
focuses on universities in Austria only. But that yaml
|
2298
|
+
file can be of help if you want to adjust it to your
|
2299
|
+
own use cases.
|
2300
|
+
|
2301
|
+
## Studium::SetAliasesBasedOnThisFile
|
2302
|
+
|
2303
|
+
This class can be used to batch-assign the main aliases used for
|
2304
|
+
asking exam questions, if a file called "exam_topics.md" exists.
|
2305
|
+
Alternatively you can pass in another file that is then used
|
2306
|
+
instead.
|
2307
|
+
|
2308
|
+
So, rather than doing:
|
2309
|
+
|
2310
|
+
setalias1 chem1
|
2311
|
+
|
2312
|
+
I can batch-assign different exam topics based on one-entry-per-line
|
2313
|
+
instead.
|
2314
|
+
|
2315
|
+
This file allows me to store exam topics in an ordered manner,
|
2316
|
+
such as first line is topic1, second line is topic2 and so
|
2317
|
+
forth. Then, once that has been done, I can hit the number 1,
|
2318
|
+
and the first exam question will be asked (belonging to
|
2319
|
+
topic2). Or I hit number 2 and the second exam topic will be
|
2320
|
+
asked, and so forth.
|
2321
|
+
|
2322
|
+
The idea behind this is that I can use the keys 1, 2, 3, 4,
|
2323
|
+
5, 6, 7, 8 and 9 to ask exam questions and thus train my
|
2324
|
+
memory in this regard. It's like an interactive trainer.
|
2325
|
+
If I want another dataset then I modify the .md file
|
2326
|
+
and re-assign. I also keep exam themes together, e. g.
|
2327
|
+
all subtopics that belong to biochemistry as a topic,
|
2328
|
+
or to cellbiology, or to genetics and so forth. It may
|
2329
|
+
be a bit difficult to explain if you have never tried this,
|
2330
|
+
so you can give it a try from the commandline perhaps -
|
2331
|
+
I use this almost daily on linux, so it has become
|
2332
|
+
"second nature" really.
|
2333
|
+
|
2334
|
+
## class ExamRegistrationAt
|
2335
|
+
|
2336
|
+
class ExamRegistrationAt can show upcoming exams. You need to
|
2337
|
+
store this information in the file lecture_information.yml, so
|
2338
|
+
there is some time investment to be done, before class
|
2339
|
+
ExamRegistrationAt is useful for you. But, once you register
|
2340
|
+
upcoming exams there, class ExamRegistrationAt can show
|
2341
|
+
which exams are the next upcoming ones. This helps allow to
|
2342
|
+
plan time for these exams.
|
2343
|
+
|
2344
|
+
Now - there are two constants that determine how many days
|
2345
|
+
ahead into the future this class will "look". So, for
|
2346
|
+
instance, if you want to see only upcoming exams for the
|
2347
|
+
next 90 days, then you should store this information in
|
2348
|
+
one of these two constants.
|
2349
|
+
|
2350
|
+
The two constants are:
|
2351
|
+
|
2352
|
+
LOOK_N_DAYS_INTO_THE_FUTURE
|
2353
|
+
LOOK_N_DAYS_INTO_THE_PAST
|
2354
|
+
|
2355
|
+
The first one is much more relevant; the second one is
|
2356
|
+
not so relevant (and it was only added fairly recently,
|
2357
|
+
in May 2022. The primary reason why the second constant
|
2358
|
+
was added was as an ad-hoc solution to not show outdated
|
2359
|
+
exam entries.).
|
2360
|
+
|
2361
|
+
## The following curricula have been completely integrated into the Studium gem so far
|
2362
|
+
|
2363
|
+
The following **table** lists which curricula have been **integrated fully** so far,
|
2364
|
+
as of **June 2022**:
|
2365
|
+
|
2366
|
+
Number | Name of the Curriculum | Curriculum Number | University | URL to the curriculum
|
2367
|
+
--------|----------------------------------------------------|--------------------|--------------------------|---------------------------------------------------------------------------------------------------------
|
2368
|
+
**1** | **Bachelor LMBT** | **033 217** | **BOKU** | https://boku.ac.at/fileadmin/data/H01000/mitteilungsblatt/MB_2019_20/MB17/033_217_Bachelorcurriculum_LMBT_2020U.pdf
|
2369
|
+
**2** | **Bachelor Umweltingenieurwissenschaften** | **033 231** | **BOKU** | https://boku.ac.at/fileadmin/data/H01000/mitteilungsblatt/MB_2020_21/MB17/Bachelorcurriculum_UIW_033_231_2021U.pdf
|
2370
|
+
**3** | **Bachelor Agrarwissenschaften** | **033 255** | **BOKU** | https://www.boku.ac.at/fileadmin/data/H01000/mitteilungsblatt/MB_2017_18/MB20/033_255_Bachelorcurriculum_AW_2018U.pdf
|
2371
|
+
**4** | **Bachelor Technische Chemie** | **033 290** | **TU** | http://www.tuwien.ac.at/fileadmin/t/studabt/downloads/Studienplaene/Oktober_2017/BachelorstudiumTechnischeChemieE033290.pdf
|
2372
|
+
**5** | **Bachelor Pharmazie** | **033 305** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Bachelorcurricula/BA_Pharmazie.pdf
|
2373
|
+
**6** | **Bachelor Molekulare Biologie** | **033 630** | **University of Vienna** | https://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Bachelorcurricula/BA_Biologie_Version2015_Juni2018.pdf
|
2374
|
+
**7** | **Bachelor Ernährungswissenschaften** | **033 638** | **University of Vienna** | https://nutrition.univie.ac.at/fileadmin/user_upload/i_ernaehrung/Download/Bachelor/Curriculum/Curriculum_Bachelor_Ernaehrungswissenschaften_2013__geringfuegige_AEnderung__2017_2018_40.pdf
|
2375
|
+
**8** | **Bachelor Chemie** | **033 662** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Bachelorcurricula/BA_Chemie.pdf
|
2376
|
+
**9** | **Bachelor Molekularbiologie** (Graz) | **033 665** | **University Graz** | https://online.uni-graz.at/kfu_online/wbMitteilungsblaetter_neu.display?pNr=14602&pDocNr=3627868&pOrgNr=14190
|
2377
|
+
________|____________________________________________________|____________________|__________________________|___________________________________________________________________________________________________________________________________________________________________________________
|
2378
|
+
**10** | **Master LMBT** | **066 418** | **BOKU** | https://www.boku.ac.at/fileadmin/data/H01000/mitteilungsblatt/MB_2017_18/MB21/066_417_Mastercurriculum_LMWT_2018U.pdf
|
2379
|
+
**11** | **Master TU Vienna Biotechnology** | **066 490** | **TU** | https://www.tuwien.ac.at/fileadmin/t/studabt/downloads/Studienplaene/Oktober_2018/MasterTechnischeChemie.pdf
|
2380
|
+
**12** | **Master Pharmazie** | **066 605** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Masterstudien/MA_Pharmazie.pdf
|
2381
|
+
**13** | **Master Immunobiologie** | **066 830** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Masterstudien/MA_Molekulare_Mikrobiologie_Mikrobielle_Oekologie_und_Immunbiologie.pdf
|
2382
|
+
**14** | **Master Biologische Chemie** | **066 863** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Masterstudien/MA_BiologischeChemie.pdf
|
2383
|
+
**15** | **Master Bioinformatik** | **066 875** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Masterstudien/MA_Bioinformatik.pdf
|
2384
|
+
**16** | **Master Genetik und Entwicklungsbiologie** | **066 877** | **University of Vienna** | http://senat.univie.ac.at/fileadmin/user_upload/s_senat/konsolidierte_Masterstudien/MA_GenetikEntwicklungsbiologie.pdf
|
2385
|
+
________|____________________________________________________|____________________|__________________________|___________________________________________________________________________________________________________________________________________________________________________________
|
2386
|
+
|
2387
|
+
|
2388
|
+
**BOKU** stands short for "Universität für Bodenkultur" (Wien / Vienna).
|
2389
|
+
|
2390
|
+
**TU** stands short for "Technische Universität" (Wien / Vienna), aka the
|
2391
|
+
"Technical University" in Vienna.
|
2392
|
+
|
2393
|
+
Keep in mind that the above table currently **only** lists curricula organized in
|
2394
|
+
**Austria**. If anyone else wants to extend this table to include other
|
2395
|
+
**european universities**, such as in Germany, feel free to do so - but the
|
2396
|
+
dataset for these universities will have to be registered **externally**
|
2397
|
+
(or at the least maintained by someone else for these other european
|
2398
|
+
universities).
|
2399
|
+
|
2400
|
+
I am willing to add required code to the studium gem, in order to make
|
2401
|
+
available any external dataset (and thus add other universities),
|
2402
|
+
though. I just can not maintain the dataset itself, since it will require
|
2403
|
+
constant adjustments. (In theory we could obtain the dataset dynamically,
|
2404
|
+
via HTTP-queries and parsing of the result, but no code doing this in
|
2405
|
+
an automated manner is presently part of the studium gem itself.)
|
2406
|
+
|
2407
|
+
Note that the studium gem keeps these "Mitteilungsblätter" stored
|
2408
|
+
in the file called <b>studium/yaml/mitteilungsblätter.yml</b>.
|
2409
|
+
|
2410
|
+
## Showing all lectures that belong to a particular curriculum
|
2411
|
+
|
2412
|
+
You can show all lectures that belong to a particular curriculum via:
|
2413
|
+
|
2414
|
+
studium --lectures-from-this-curriculum=geodäsie
|
2415
|
+
studium --lectures-from-this-curriculum=217
|
2416
|
+
|
2417
|
+
This does not work perfectly well, so if in doubt use the
|
2418
|
+
curriculum id, as a number.
|
2419
|
+
|
2420
|
+
## The very important file called lecture_information.yml
|
2421
|
+
|
2422
|
+
Since as of <b>July 2022</b> the very important file called
|
2423
|
+
<b>lecture_information.yml</b> now resides at:
|
2424
|
+
|
2425
|
+
studium/lib/studium/lecture_information/lecture_information.yml
|
2426
|
+
|
2427
|
+
It seemed better to me to put it into a separate directory, considering
|
2428
|
+
it is just about <b>the most important .yml file of this project</b>.
|
2429
|
+
|
2430
|
+
Remember that the file caters primarily to universities in Austria,
|
2431
|
+
but since it is ultimately just one huge hash (see the content),
|
2432
|
+
you can simply add more .yml files to it, or modify the hash that
|
2433
|
+
you get to your liking - so the studium gem is, in principle
|
2434
|
+
extensible to <b>accomodate datasets from different universities</b>.
|
2435
|
+
I may even add more web-scraping means to allow users to automatically
|
2436
|
+
determine all lectures from a given curriculum at other universities -
|
2437
|
+
but for now (2022) this is not yet possible.
|
2438
|
+
|
2439
|
+
## Determining the runmode of the Studium gem
|
2440
|
+
|
2441
|
+
The runmode can be determined via <b>Studium.set_runmode()</b>.
|
2442
|
+
|
2443
|
+
## Deprecations within the Studium gem
|
2444
|
+
|
2445
|
+
This subsection keeps track of some deprecations of this project.
|
2446
|
+
|
2447
|
+
The constant <b>EXAM_TOPICS</b>, which used to be:
|
2448
|
+
|
2449
|
+
EXAM_TOPICS = "#{Studium.project_base_directory?}exam_topics/"
|
2450
|
+
|
2451
|
+
as well as "aliases" to it, such as DIRECTORY_TO_THE_EXAM_TOPICS
|
2452
|
+
or EXAM_TOPICS_DIRECTORY, was deprecated as of <b>July 2022</b>.
|
2453
|
+
|
2454
|
+
If you want to obtain the exam-topics directory then you should
|
2455
|
+
consistently use the following method instead:
|
2456
|
+
|
2457
|
+
Studium.exam_topics_directory?
|
2458
|
+
|
2459
|
+
The old code will be published here for some time longer, but
|
2460
|
+
eventually it may be removed entirely:
|
2461
|
+
|
2462
|
+
# ========================================================================= #
|
2463
|
+
# === EXAM_TOPICS
|
2464
|
+
#
|
2465
|
+
# This constant will store where the exam topics are stored on a
|
2466
|
+
# given computer system.
|
2467
|
+
#
|
2468
|
+
# The path will be relative to the PROJECT_BASE_DIRECTORY constant.
|
2469
|
+
#
|
2470
|
+
# Note that this is a constant though - it is recommended to use
|
2471
|
+
# the @exam_topics variable instead if you need the variable
|
2472
|
+
# to be dynamic.
|
2473
|
+
#
|
2474
|
+
# This may, for example, have a value such as:
|
2475
|
+
#
|
2476
|
+
# /Programs/Ruby/2.5.1/lib/ruby/site_ruby/2.5.0/studium/exam_topics/
|
2477
|
+
#
|
2478
|
+
# ========================================================================= #
|
2479
|
+
EXAM_TOPICS = "#{Studium.project_base_directory?}exam_topics/"
|
2480
|
+
# ======================================================================= #
|
2481
|
+
# === DIRECTORY_TO_THE_EXAM_TOPICS
|
2482
|
+
# ======================================================================= #
|
2483
|
+
DIRECTORY_TO_THE_EXAM_TOPICS = EXAM_TOPICS
|
2484
|
+
# ======================================================================= #
|
2485
|
+
# === EXAM_TOPICS_DIRECTORY
|
2486
|
+
#
|
2487
|
+
# Same as above.
|
2488
|
+
# ======================================================================= #
|
2489
|
+
EXAM_TOPICS_DIRECTORY = EXAM_TOPICS
|
2490
|
+
|
2491
|
+
In <b>July 2022</b> the old method called <b>Studium.ensure_main_encoding()</b>
|
2492
|
+
was deprecated. It did no longer seem necessary to have it, as UTF-8
|
2493
|
+
is used by default now.
|
2494
|
+
|
2495
|
+
However had, perhaps in the future this may have to be re-enabled in
|
2496
|
+
one way or another. I will keep the code here, but it may also be that
|
2497
|
+
this code will never be re-added, in which case a future release of
|
2498
|
+
the studium gem may remove the following subsection. Either way here
|
2499
|
+
goes:
|
2500
|
+
|
2501
|
+
# ========================================================================= #
|
2502
|
+
# === Studium.ensure_main_encoding
|
2503
|
+
#
|
2504
|
+
# This method will try to ensure the main encoding in use. This
|
2505
|
+
# presently works for both Arrays and Strings; other classes are
|
2506
|
+
# not supported (but they are also not as important as Arrays
|
2507
|
+
# and Strings really; possibly excluding class Hash).
|
2508
|
+
# ========================================================================= #
|
2509
|
+
def self.ensure_main_encoding(i)
|
2510
|
+
copy = i
|
2511
|
+
use_this_encoding = @use_this_encoding
|
2512
|
+
# ======================================================================= #
|
2513
|
+
# === Handle Array next
|
2514
|
+
# ======================================================================= #
|
2515
|
+
if copy.is_a? Array
|
2516
|
+
copy = copy.map {|entry|
|
2517
|
+
if entry.is_a? String
|
2518
|
+
unless entry.encoding.to_s.include? use_this_encoding
|
2519
|
+
entry = entry.force_encoding(use_this_encoding)
|
2520
|
+
end
|
2521
|
+
end
|
2522
|
+
entry
|
2523
|
+
}
|
2524
|
+
# ======================================================================= #
|
2525
|
+
# === Handle Hash next
|
2526
|
+
# ======================================================================= #
|
2527
|
+
elsif copy.is_a? Hash
|
2528
|
+
new_hash = {}
|
2529
|
+
copy.each_pair {|key, value|
|
2530
|
+
unless key.encoding.to_s.include? use_this_encoding
|
2531
|
+
key = key.dup if key.frozen?
|
2532
|
+
unless key.is_a? Symbol
|
2533
|
+
key = key.force_encoding(use_this_encoding)
|
2534
|
+
end
|
2535
|
+
end
|
2536
|
+
if value.is_a? Array
|
2537
|
+
array = Studium.ensure_main_encoding(array)
|
2538
|
+
end
|
2539
|
+
new_hash[key] = ensure_main_encoding(value)
|
2540
|
+
}
|
2541
|
+
copy = new_hash
|
2542
|
+
# ======================================================================= #
|
2543
|
+
# === Handle String next
|
2544
|
+
# ======================================================================= #
|
2545
|
+
elsif copy.is_a? String
|
2546
|
+
unless copy.encoding.to_s.include? use_this_encoding
|
2547
|
+
copy = copy.dup if copy.frozen?
|
2548
|
+
copy = copy.force_encoding(use_this_encoding)
|
2549
|
+
end
|
2550
|
+
end
|
2551
|
+
return copy
|
2552
|
+
end
|
2553
|
+
|
2554
|
+
In <b>July 2022</b> the constant:
|
2555
|
+
|
2556
|
+
FILE_LECTURE_INFORMATION = "#{PROJECT_YAML_DIRECTORY}lecture_information.yml"
|
2557
|
+
|
2558
|
+
was deprecated. Use the toplevel instance variable @file_lecture_information
|
2559
|
+
instead, or the method <b>Studium.file_lecture_information</b>.
|
2560
|
+
The constant <b>FILE_LECTURE_ALIASES</b> was also deprecated in <b>July
|
2561
|
+
2022</b>, as well as the constant <b>FILE_CURRICULA</b>.
|
2562
|
+
|
2563
|
+
The same counts for the constant <b>FILE_IMPORTANT_EXAMS</b>. In general,
|
2564
|
+
methods are now more important, so use the replacement method called
|
2565
|
+
<b>Studium.file_important_exams</b>.
|
2566
|
+
|
2567
|
+
The constant:
|
2568
|
+
|
2569
|
+
ALPHABET = ('a'..'z').to_a
|
2570
|
+
|
2571
|
+
was moved into the only .rb file that needs it - it was part of
|
2572
|
+
constants.rb before <b>July 2022</b>.
|
2573
|
+
|
2574
|
+
The following constant was removed in <b>July 2022</b>:
|
2575
|
+
|
2576
|
+
# ========================================================================= #
|
2577
|
+
# === FILE_UPCOMING_PRACTICAL_COURSES
|
2578
|
+
#
|
2579
|
+
# This file is for a .yml file that keeps track of upcoming practical
|
2580
|
+
# courses. In particular, this may be helpful in order to determine
|
2581
|
+
# which practical courses may overlap with one another.
|
2582
|
+
# ========================================================================= #
|
2583
|
+
# FILE_UPCOMING_PRACTICAL_COURSES =
|
2584
|
+
# "#{STUDIUM_YAML_DIR}WS2017/upcoming_practical_courses.yml"
|
2585
|
+
|
2586
|
+
It is probably no longer needed, because the file lecture_information.yml
|
2587
|
+
can indicate in which practical courses we are registered now.
|
2588
|
+
|
2589
|
+
The constant ARRAY_TITLE_OF_THE_INDIVIDUAL_CURRICULA was also disabled
|
2590
|
+
as of <b>July 2022</b> - each individual curricula now has the title
|
2591
|
+
on its very second line:
|
2592
|
+
|
2593
|
+
# ========================================================================= #
|
2594
|
+
# === ARRAY_TITLE_OF_THE_INDIVIDUAL_CURRICULA
|
2595
|
+
#
|
2596
|
+
# This constant is mostly on an ad-hoc basis in that we will register
|
2597
|
+
# the title of all individual curricula. This can then be used by
|
2598
|
+
# Studium::DetermineCurricula in particular to determine which
|
2599
|
+
# courses ought to be shown.
|
2600
|
+
# ========================================================================= #
|
2601
|
+
ARRAY_TITLE_OF_THE_INDIVIDUAL_CURRICULA = [
|
2602
|
+
'Bachelorcurriculum Informatik und molekulare Biologie',
|
2603
|
+
'Bachelorcurriculum (Bio)Informatik und molekulare Biotechnologie, unter Berücksichtigung medizinisch-immunologischer Aspekte',
|
2604
|
+
'Bachelorcurriculum Vector-based strategies in Life Sciences, Molecular Medicine and Biotechnology'
|
2605
|
+
]
|
2606
|
+
|
2607
|
+
The constant <b>PASSED_EXAMS_PER_MONTH</b>:
|
2608
|
+
|
2609
|
+
PASSED_EXAMS_PER_MONTH = FILE_PASSED_EXAMS_PER_MONTH
|
2610
|
+
|
2611
|
+
Was just an alias in the past. It has been removed in <b>July 2022</b>.
|
2612
|
+
|
2613
|
+
If you have to, use the longer constant name called
|
2614
|
+
<b>FILE_PASSED_EXAMS_PER_MONTH</b>. The constant called
|
2615
|
+
<b>FILE_DIRECTORY_TO_THE_EXAM_TOPICS</b> was also
|
2616
|
+
removed.
|
2617
|
+
|
2618
|
+
The constant <b>DIRECTORY_EXAM_TOPICS</b> was removed as well.
|
2619
|
+
|
2620
|
+
# ========================================================================= #
|
2621
|
+
# === DIRECTORY_EXAM_TOPICS
|
2622
|
+
#
|
2623
|
+
# Determine where we can find the exam topics, as constant.
|
2624
|
+
# ========================================================================= #
|
2625
|
+
DIRECTORY_EXAM_TOPICS = MY_EXAM_TOPICS
|
2626
|
+
|
2627
|
+
## Vorbesprechungen / Preliminary meetings
|
2628
|
+
|
2629
|
+
Some courses require a date before the actual course week, which we
|
2630
|
+
will call "preliminary meetings" (in german, "Vorbesprechung" or
|
2631
|
+
"Vorbesprechungstermin"). In July 2022 the name was changed to
|
2632
|
+
preparatory_meeting.
|
2633
|
+
|
2634
|
+
The Studium project supports this keeping track of such a preparatory
|
2635
|
+
meeting. The corresponding entry that has to exist, in the
|
2636
|
+
file **lecture_information.yml**, is called
|
2637
|
+
"preparatory_meeting:".
|
2638
|
+
|
2639
|
+
The **class PreparatoryMeeting** can show upcoming preliminary
|
2640
|
+
meetings. That way you should not miss the mandatory attendance
|
2641
|
+
part anymore of some courses.
|
2642
|
+
|
2643
|
+
The name <b>Vorbesprechungen</b> is kept as a backwards "alias"
|
2644
|
+
to this new class.
|
2645
|
+
|
2646
|
+
## Returning the dataset of a specific exam topic
|
2647
|
+
|
2648
|
+
If you have a need to return the dataset of a specific
|
2649
|
+
exam topic, as an Array, then you can use the following
|
2650
|
+
API:
|
2651
|
+
|
2652
|
+
array = Studium.return_dataset_for_this_exam_topic('geology')
|
2653
|
+
array = Studium.return_dataset_for_this_exam_topic('genetics')
|
2654
|
+
|
2655
|
+
And so forth. This method appeared to be useful to use it on
|
2656
|
+
some website, for instance.
|
2657
|
+
|
2658
|
+
## Displaying curriculum modules on the commandline
|
2659
|
+
|
2660
|
+
<b>class Studium::Curricula::Modules::DisplayOnTheCommandline</b>
|
2661
|
+
can display each module of a specific curriculum on the commandline.
|
2662
|
+
|
2663
|
+
This only really works very well for individual curricula. But in
|
2664
|
+
principle this class could be extended to work with <b>all</b>
|
2665
|
+
curricula in general.
|
2666
|
+
|
2667
|
+
## class Studium::ReturnNEctsFromThisUrl
|
2668
|
+
|
2669
|
+
<b>class Studium::ReturnNEctsFromThisUrl</b> can be used to
|
2670
|
+
determine the number of ECTS points of a given lecture.
|
2671
|
+
|
2672
|
+
Pass the remote URL to this class in order for this to
|
2673
|
+
work.
|
2674
|
+
|
2675
|
+
Example:
|
2676
|
+
|
2677
|
+
Studium::ReturnNEctsFromThisUrl.new('https://online.boku.ac.at/BOKUonline/wbLv.wbShowLVDetail?pStpSpNr=278600')
|
2678
|
+
|
2679
|
+
## Java code pertaining to the studium gem
|
2680
|
+
|
2681
|
+
Since about two years, give or take, say starting in
|
2682
|
+
the year 2020, Java code has been added to the
|
2683
|
+
studium gem - both for the commandline, as well as
|
2684
|
+
GUIs. This is highly experimental still and not
|
2685
|
+
very extensive.
|
2686
|
+
|
2687
|
+
Most work goes into <b>AskExamQuestion.java</b>
|
2688
|
+
right now, until it is possible to work with the
|
2689
|
+
Studium gem from the commandline, in particular
|
2690
|
+
on Windows. Then when this works alright, we may
|
2691
|
+
extend the Swing and JavaFX bindings, to make it
|
2692
|
+
more convenient to work with the project via a
|
2693
|
+
GUI - but first the commandline has to work
|
2694
|
+
very well.
|
2695
|
+
|
2696
|
+
Once that works ok-ish the studium gem should be
|
2697
|
+
more useful on windows too; Java works fairly
|
2698
|
+
well on windows and is quite fast. Speed is one
|
2699
|
+
of the few things Java is better than ruby. In
|
2700
|
+
the long run, though, it may be ideal to use
|
2701
|
+
truffleruby or jruby to bridge the gap between
|
2702
|
+
these two worlds. Stay tuned for more to come
|
2703
|
+
in this regard.
|
2704
|
+
|
2705
|
+
## Generating .pdf files
|
2706
|
+
|
2707
|
+
You can generate some .pdf files about exam-topics.
|
2708
|
+
|
2709
|
+
For example, for the topic **amg**, you can generate a .pdf file
|
2710
|
+
through:
|
2711
|
+
|
2712
|
+
studium --generate-pdf-for=amg1
|
2713
|
+
|
2714
|
+
Do note that this functionality depends on the gem called **prawn**.
|
2715
|
+
|
2716
|
+
Here are more examples for pdf-generation:
|
2717
|
+
|
2718
|
+
studium --generate-pdf-for=biotech1
|
2719
|
+
studium --generate-pdf-for=biotech2
|
2720
|
+
studium --generate-pdf-for=virus1
|
2721
|
+
studium --generate-pdf-for=virus2
|
2722
|
+
|
2723
|
+
Note that most of the functionality related to PDF-files can be
|
2724
|
+
found under the directory <b>studium/utility_scripts/pdf/</b>.
|
2725
|
+
|
2726
|
+
Since as of <b>August 2022</b> it is now possible to
|
2727
|
+
generate a huge .pdf file that contains ALL the exam
|
2728
|
+
questions. So this is using the same functionality as
|
2729
|
+
above, but it will integrate **all** topics. Beware,
|
2730
|
+
this will lead to a truly huge .pdf file:
|
2731
|
+
|
2732
|
+
The commandline for this functionality can be invoked
|
2733
|
+
by issuing any of the following:
|
2734
|
+
|
2735
|
+
studium --mega-pdf
|
2736
|
+
studium --monster-pdf
|
2737
|
+
studium --monster
|
2738
|
+
|
2739
|
+
Note that this may take about 30 seconds or longer,
|
2740
|
+
and the generated .pdf file will easily have more
|
2741
|
+
than 1449 pages. So this is not too terribly useful
|
2742
|
+
for most people, but just in case this functionality
|
2743
|
+
exists, so there you go.
|
2744
|
+
|
2745
|
+
|
2746
|
+
## Contact information and mandatory 2FA coming up in 2022
|
2747
|
+
|
2748
|
+
If your creative mind has ideas and specific suggestions to make this gem
|
2749
|
+
more useful in general, feel free to drop me an email at any time, via:
|
2750
|
+
|
2751
|
+
shevy@inbox.lt
|
2752
|
+
|
2753
|
+
Before that email I used an email account at Google gmail, but in **2021** I
|
2754
|
+
decided to slowly abandon gmail for various reasons. In order to limit this
|
2755
|
+
explanation here, allow me to just briefly state that I do not feel as if I
|
2756
|
+
want to promote any Google service anymore, for various reasons.
|
2757
|
+
|
2758
|
+
Do keep in mind that responding to emails may take some time, depending on
|
2759
|
+
the amount of work I may have at that moment.
|
2760
|
+
|
2761
|
+
In 2022 rubygems.org decided to make 2FA mandatory for every gem owner:
|
2762
|
+
see https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
|
2763
|
+
|
2764
|
+
As I can not use 2FA, for reasons I will skip explaining here (see
|
2765
|
+
various github issue discussions in the past), this effectively means that
|
2766
|
+
Betty Li and others who run the show at rubygems.org will perma-ban me
|
2767
|
+
from using rubygems as a developer.
|
2768
|
+
|
2769
|
+
As I disagree with that decision completely, this will mean that all my
|
2770
|
+
gems will be removed from rubygems.org prior to that sunset date, e. g.
|
2771
|
+
before they permanently lock me out from the code that I used
|
2772
|
+
to maintain. It is pointless to want to discuss this with them anymore -
|
2773
|
+
they have made up their minds and decided that you can only use
|
2774
|
+
the code if 2FA is in place, even though the code itself works just
|
2775
|
+
fine. If you don't use 2FA you are effectively locked out from your
|
2776
|
+
own code; I consider this a malicious attack. See also how they limited
|
2777
|
+
discussions to people with mandatory 2FA on the ruby-bugtracker, thus
|
2778
|
+
banning everyone permanently without 2FA:
|
2779
|
+
|
2780
|
+
https://bugs.ruby-lang.org/issues/18800
|
2781
|
+
|
2782
|
+
Guess it may indeed be time to finally abandon ruby - not because
|
2783
|
+
ruby is a bad language, but there are people now in charge who
|
2784
|
+
really should not be part of ruby in the first place.
|
2785
|
+
|