Drasil Research Group Meeting, 3pm, Monday July 29, 2024, ITB/225

[smiths]

0. Thoughts on Dr. Sagar and Dr. Akbar
1. Blockers? (@NoahCardoso)
2. Vectors in Drasil (@BilalM04)
3. Add citation to original (manual) works from each case study #3562 (@TRISHI-L)
4. HTML: Figures should have Figure X: in their figcaption and references to figures should be prettier. #702 (@TRISHI-L)
5. Posters

regrets: @balacij, @B-rando1

[smiths]

@B-rando1, @NoahCardoso, @BilalM04 and @TRISHI-L please provide your summarizes.

[B-rando1]

Weekly Summary

• I spent a lot of the week getting Drasil ready for procedural languages. On Thursday I got everything done far enough that we can generate procedural Julia code! Switched the Julia renderer to ProcProg #3868
  • There was a lot of duplication required in drasil-code because of some OO assumptions in the types involved. I plan to look into those and see if we can reorganize the types in order to merge some of the functions.
• I looked into Change constDecDef implementation in Python #2179 and successfully made it capitalize constants in Python. There are a few issues we should eventually solve, the first one being Improve variable name conflict detection in GOOL #3867.
• Now that the Julia renderer is mostly stable, I need to return to Local scope in Julia #3821. This has two parts to it:
  • Tracing the scope of variable creations to their source in drasil-code. This is a bit tedious, but has been mostly straightforward.
  • Adding global variable declarations in Julia. Fortunately Julia doesn't mind if we go a little overkill with them, which should make it easier to get an initial fix out. Doing it properly will require a few more changes, though.

Note that I am taking Monday off, so I won't be at the meeting.

[BilalM04]

Weekly Summary

This week the mdBook project was completed and merged into main. I worked on several issues in the backlog that @balacij assigned to me, as well as issues I created myself. Having become quite familiar with drasil-printers, GitHub workflows, and shell scripts, I found myself particularly drawn to those issues. I was also introduced to the project involving vectors that @NoahCardoso and I would work on.

• Fixed the PDF deployment scripts and workflow (Fixed PDF deployment #3870).
• Hosted the mdBook examples on the website (Hosting mdBook examples on website #3872).
• Fixed the rendering of the multiplication operator in LaTeX (Updated Mul operator rendering #3881).
• Fixed the placement of figures in the generated TeX/PDF SRS (Fixed placement of figures in TeX PDF #3885).
• Other minor PRs:
  • Add new example in benefits-of-drasil wiki #3887
  • Crop Images in Datafiles with Excessive Whitespace #3886
  • Fix build failiure in main #3874
  • Build update and minor code cleanup #3880
• Proposed a solution for SRS document formatting problem for long labels #1877 (comment).
• Started looking into the vectors project. @balacij suggested that as a first step, I should go through the issue tracker to determine what exactly needs to be done. Working on that while also working on issues here and there.

Agenda

At the moment, I am going through the issue tracker to get and understanding of the current state of vectors and what needs to be done. I am still quite unsure/confused as I have not dealt with that part of Drasil yet, but I'm sure my understanding of the project will improve as I progress.

If anyone has useful information about vectors in Drasil or can guide me in the right direction, it would be great to discuss this in the meeting.

[Xinlu-Y]

Weekly Summary

• I explored the specifics of Drasil related to document and design.
• Investigated the principle of references and continued working on resolving related issues ( Add citation to original (manual) works from each case study #3562) (HTML: Figures should have Figure X: in their figcaption and references to figures should be prettier. #702)

Agenda/ Blockers

• My initial approach was to create web link references using makeURI in the function externalLinkRef, and then add these references using namedRef as part of overviewParagraph to generate this paragraph. However, I am encountering issues with adding external link references to the project documentation:

projectile: Reference: projectileSRSLink not found in ReferenceMap
CallStack (from HasCallStack):
  error, called at lib/Database/Drasil/ChunkDB.hs:116:24 in drasil-database-0.1.1.0-K6UHWiVtYpB6Vm3pvDkt1g:Database.Drasil.ChunkDB
make: *** [Makefile:299: projectile_gen] Error 1

• All documents use the same template (code/drasil-docLang/lib/Drasil/Sections/Introduction.hs) to generate the introduction section. In the introduction modules of different documents, the external SRS manual links that need to be referenced vary. I am still familiarizing myself with the functionalities of all the modules, I am re-evaluating how to ensure that the relevant functions are correctly defined and implemented in the appropriate modules.

[NoahCardoso]

Weekly Summary

• I have added sets in all of the glassbr examples (not Julia). I mostly worked on improving and reviewing the drasil-GOOL and drasil-code code that I wrote. Adding Sets #3878
• I have mostly finished Assigning to a variable before use in a conditional #3869
• Started to look into vectors in GOOL project that I will be starting with @BilalM04

Agenda

• next week I will finish my Adding Sets to Drasil pr
• I will start working more on adding Strict Data as well as Stan Add stan and weeder to our dev. workflow #3710

[balacij]

@TRISHI-L Coincidentally, we have a section in the wiki dedicated to that issue. If it isn't helpful enough, when you ultimately resolve your issue, it would be appreciated if you could update it :)

[JacquesCarette]

There's a possibility of my being able to attend this one. We'll see.

Re: Vectors. Basically Drasil currently doesn't really know about vectors - the current implementation is a hack. We need to be able to declare them, create them, index them, and manipulate them. We also need vectors to have both fixed (i.e. known at code generation time) and arbitrary (i.e. unknown at generation time) vectors. So the 'size' of a vector will need to handle both (positive) integers and expressions denoting same.

[smiths]

That would be great if you could attend @JacquesCarette, especially because @balacij will be absent from this one. (@samm82 I'll ask you to do the IT support for this meeting again, if you don't mind.)

[smiths]

We covered all agenda items.