| 
261 | 261 |        potentially establishing a new standard for high-performance genomic data analysis.  | 
262 | 262 |       proposal: /assets/docs/Aditya_Pandey_GSoC2025.pdf  | 
263 | 263 |       mentors: Martin Vassilev, Jonas Rembser, Fons Rademakers, Vassil Vassilev  | 
 | 264 | + | 
 | 265 | +- name: Petro Mozil  | 
 | 266 | +  photo: PetroMozil.jpeg  | 
 | 267 | +  info: "Google Summer of Code 2025 Contributor"  | 
 | 268 | + | 
 | 269 | +  education: "Bachelor of Computer Science, Ukrainian Catholic University, Ukraine"  | 
 | 270 | +  github: "https://github.com/pmozil"  | 
 | 271 | +  active: 1  | 
 | 272 | +  linkedin: "https://www.linkedin.com/in/petro-mozil-a94583170/"  | 
 | 273 | +  projects:  | 
 | 274 | +    - title: "Enabling support for STL concurrency primitives in CLAD"  | 
 | 275 | +      status: Ongoing  | 
 | 276 | +      description: |  | 
 | 277 | +        Clad recursively iterates over the syntax tree to check whether a given   | 
 | 278 | +        statement should be differentiated. Each function that is called from   | 
 | 279 | +        inside of a differentiated function should be differentiated as well,   | 
 | 280 | +        and so should any object method. The main issue for clad is that std::thread is an object,   | 
 | 281 | +        and thus as a type that should be differentiated However, std::thread shouldn’t   | 
 | 282 | +        be differentiated, the function inside of it should.   | 
 | 283 | +        Some of STL’s concurrency primitives face the same problem -   | 
 | 284 | +        the methods in them should not be differentiated,   | 
 | 285 | +        and only the location of where they were called should be preserved.  | 
 | 286 | +      proposal: /assets/docs/petro_mozil_promosal_GSoC_2025.pdf  | 
 | 287 | +      mentors: Martin Vassilev, David Lange  | 
264 | 288 | 
 
  | 
265 | 289 | - name: Salvador de la Torre Gonzalez  | 
266 | 290 |   info: "Google Summer of Code 2025 Contributor"  | 
 | 
0 commit comments