Drasil Meeting, Tuesday, May 20, 3:00 pm, ITB/225

[smiths]

1. Blockers for @jackwyand.

• Referencing this comment, it is unclear to me how/where code generation takes place, making it difficult for me to get started on issues brought up in the comment (Order of reading inputs, deriving pseudo-input values, and checking constraints is incorrect #4075 for example)
• Discuss how to clean up extra constraint-related chunks and fix problems that arose in GlassBR - plateLen, plateWidth, charWeight, pbTol, and tNT inserted twice in SymbolMap #4064

2. Blockers for @sarrasoussia: While working on the refactoring issue, I had to understand the main reason why we need to refactor in the first place.
   The GProc, OO, and CLike division in Drasil makes things clearer, but sometimes there's overlap between the layers, which I feel makes it harder to model hybrid languages (like C++ or Python).
   I was thinking maybe we could group renderers and helpers by language features instead like control (loops, switch, etc.), functions, types, variables, files…
   That would need more coordination between modules, though.

3. Geometric Algebra in Drasil PR

4. @balacij : physical constraints == implicit constraints on physical quantities ++ ? Related to: Order of reading inputs, deriving pseudo-input values, and checking constraints is incorrect #4075

[smiths]

@JacquesCarette what time is good for you for next week's meeting? I'm normally good for the same time as this past week (1:30 pm), but I have an eye doctor appointment next week. Could you do 3 pm?

[JacquesCarette]

Having it normally at 1:30 is good for me. Doing it at 3pm next week is fine too - I'll have to move a meeting, but it is quite moveable.

[smiths]

Okay, for next week, we'll have the meeting at 3pm. I've asked Mary to book us a room.

For subsequent weeks, we set a recurring meeting for Tuesdays at 1:30 pm. I'll ask Mary to book that as a recurring meeting.

[smiths]

The location for our meeting today is ITB/225.

[smiths]

All agenda items were covered, so we can close this issue.