Comments (3)
This code concerns the automatic generation of chunk names. I don't want to have chunk names that are too long, because they are shown in a Markdown version of the problem set and also are used to name all HTML identifiers (perhaps performance goes down a bit, if all IDs are super long). I changed RTutor just now in a different fashion. Chunks are now just named with the exercise counter as a prefix instead of the 20 first characters of the exercise name. Makes more sense and the IDs are even shorter now. You also should not have any problems with your exercise names anymore.
from rtutor.
I integrated your changes and all technical aspects work fine.
I am however worried about maintainability down the line and effects on the transparency of the submission files if the course is actively in development. (Which by the way is broadly our plan: To have constant and continuous improvement on all courses to achieve maximum quality and keeping them up-to-date)
Take for example a course (or course chapter) where there exist several exercises. One of the exercises shall be expanded. This in turn makes it to long for easy digestion. It is split up in two parts. As a result all later chunks get renamed. Even though no change took place in the later exercises they can't trivially be matched across problem set versions, making it harder to analyze the submission files of a course.
Especially regarding the submission files it might be helpful to include (possibly optional) additional indicators to the chunks/Exercises (be it in sub$by.chunk, sub$by.ex and/or in sub$log.txt). One could for example include the name of the Exercise as an additional column to the data frames. I think this would be a comparatively cheap but powerful change.
Ideally one could additionally set optional names to chunks which are persistent and not subject to changes of the exercise name and earlier chunks. This would make it more time-consuming to build the problem set but a lot easier to have say graphical and in depth analyses even for problem sets which change very dynamically.
from rtutor.
I don't see that this is problematic. If you have different versions of your problem set (and continuous improvement is definitely a good idea) then you should also keep for every version the corresponding rps file and the Rmd solution file. Using the rps file you can always match the chunks to the corresponding exercises. I think that at some functions of RTutorSAGI for analysing the solutions require anyway that you provide the corresponding rps file.
from rtutor.
Related Issues (20)
- Duplicated exercise names cause errors HOT 1
- Pre-run code chunks? HOT 4
- Installation issue; HOT 6
- Running example chunk HOT 5
- Test that would allow open text HOT 6
- Controlling the width of the quizzes HOT 2
- Window Position when clicking on "Go to next exercise..." HOT 2
- Executing invisible code HOT 4
- Deletion of columns deletes more columns than expected HOT 3
- New Options regarding rtutor.app.skel HOT 4
- "Go to next exercise" Button does not trigger generation of code chunks HOT 2
- Desired behavior of check.assign HOT 1
- Width of Quizzes HOT 2
- Major update Branch LeverageData (mostly regarding quizzes) HOT 4
- hints based on check.call HOT 9
- highlight boxes HOT 5
- Updates in RTutor Main Branch HOT 5
- Question regarding mark_utf8 HOT 1
- Warning: Error in : colourInput() has been moved to the 'colourpicker' package. HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rtutor.