kaist-cp / kaist-cp.github.io Goto Github PK

The bibliography information on students' pages look weird, due to line breaks.

I guess it comes from _include/person_contact.md.
It seems line break happens if a person does not have an orcid information.

Trying to access base URL + path starts with a character 'c' like 'https://cp.kaist.ac.kr/c*', the page doesn't show proper contents but it shows sentence '404 Not Found' only. It is a very strange situation. Because if there is no path starts with 'c' on the server, the server should show 404 page we customed.

This situation only appears in cp.kaist.ac.kr, not in local.

Lectures가 index.md, _people/jeehoon.kang.md 두 페이지에 있습니다.

This is a meta issue on personal websites.

• Awards and Honors
• Invited Talks
• Services
• Research
• Photo?
• Thesis

Browser: Firefox version 95.0

Bug:

1. Font size in navigation bar is too big that it goes off the screen, leading to a horizontal scroll bar at the bottom.
2. Font size is too big on Firefox.
3. It works on Chromium Version 96.0.4664.45, there is no bug on chrome iOS app too.

Reason:
I think the bug comes from jekyll itself.
On Chrome, jekyll use -webkit-text-size-adjust: 100%; for the whole html. But this property is not capable with Firefox, in Firefox we need to use font-size-adjust: 0.45.

I tried for a while to fix the bug but I can't get it work....I am opening this issue just let other's know.

• Low-cost verification of OS: toy OS's have been formally verified so far, but only with a great labor cost.
  It doesn't scale to more realistic OS's. I'd like to formally verify them with lower cost.
  The key idea is leveraging Rust type system as a static analyzer. We can the safety guarantee (for those written in the safe part of Rust) "for free."

• Compiler for FPGA: FPGA's parallelism is unparalleled with that of CPUs.
  FPGAs are particularly beneficial when control flow is not so regular. (For programs with regular control flow, GPUs would be better.)
  But the main challenge in using FPGA is programmability. It's just too difficult.
  There's prior work on compiling C to FPGA, but it suffers from many problems.
  We aim to design a new high-level language that better suits with FPGA, and build a compiler for the language to FPGA.

• persistent synchronization patterns verification