• About
    • Contact

/root

  • Identifying the Unauthorized Use of Examination Material

    February 4th, 2024

    An interesting paper about a strategy that was created after a cheating scandal involving Canada’s Medical Council of Canada Qualifying Examination (MCCQE) in 2004.

    After learning which questions were circulated, MCCQE administrators evaluated exams by comparing answers of compromised questions with the answers of noncompromised questions.

    https://journals.sagepub.com/doi/abs/10.1177/0163278709356192

  • USMLE and Recalls Scandal

    February 4th, 2024

    “The selling and buying of USMLE questions online have become rampant in recent years, particularly by groups within the international medical graduate (IMG) community, according to multiple IMGs who shared their concerns with Medscape Medical News over the past month. Sellers operate under pseudonyms across social media platforms and charge anywhere from $300 to $2000 for questions, Medscape research shows.”

    “The statistical probability that you would have three or more candidates in the same year, scoring in the 99th percentile worldwide, belonging to a small geographical area is extremely low.” 

    https://www.medscape.com/viewarticle/us-board-discloses-cheating-grads-say-problem-rampant-2024a10002aj

  • My most popular Reddit post

    February 4th, 2024
  • kdesrc-build keeps failing !!

    February 4th, 2024

    Checking the build log:

    > cat /home/chris/kde/src/log/2024-02-04-01/kiconthemes/build.log
    # kdesrc-build running: 'ninja' '-j' '4'
    # from directory: /home/chris/kde/build/kiconthemes
    [0/1] Re-running CMake...
    CMake Deprecation Warning:
    Support for "Extra Generators" like

    Kate

    is deprecated and will be removed from a future version of CMake. IDEs may
    use the cmake-file-api(7) to view CMake-generated project build trees.


    --

    Installing in /home/chris/kde/usr. Run /home/chris/kde/build/kiconthemes/prefix.sh to set the environment for KIconThemes.
    CMake Error at /home/chris/kde/usr/lib/cmake/KF6BreezeIcons/KF6BreezeIconsConfig.cmake:32 (include):
    include could not find requested file:

    /home/chris/kde/usr/lib/cmake/KF6BreezeIcons/KF6BreezeIconsTargets.cmake
    Call Stack (most recent call first):
    CMakeLists.txt:62 (find_package)


    CMake Warning (dev) at /home/chris/kde/usr/share/ECM/modules/ECMQmlModule6.cmake:49 (message):
    The CLASSNAME argument to ecm_add_qml_module is deprecated for Qt 6; Use
    CLASS_NAME instead.
    Call Stack (most recent call first):
    src/qml/CMakeLists.txt:1 (ecm_add_qml_module)
    This warning is for project developers. Use -Wno-dev to suppress it.

    -- The following features have been enabled:

    * DESIGNERPLUGIN, Build plugin for Qt Designer

    -- The following OPTIONAL packages have been found:

    * OpenGL
    * XKB (required version >= 0.5.0), XKB API common to servers and clients., <http://xkbcommon.org>
    * Qt6GuiTools (required version >= 6.7.0)
    * WrapVulkanHeaders
    * Qt6Quick (required version >= 6.5.0)
    * Qt6CoreTools (required version >= 6.7.0)
    * Qt6DBusTools (required version >= 6.7.0)
    * Qt6QmlTools (required version >= 6.7.0)
    * Qt6WidgetsTools (required version >= 6.7.0)
    * Qt6Test (required version >= 6.5.0)

    -- The following REQUIRED packages have been found:

    * ECM (required version >= 5.249.0), Extra CMake Modules., <https://commits.kde.org/extra-cmake-modules>
    * Qt6Svg (required version >= 6.5.0)
    * Qt6Core (required version >= 6.5.0)
    * KF6Archive (required version >= 5.249.0)
    * Gettext
    * KF6I18n (required version >= 5.249.0)
    * Qt6DBus (required version >= 6.5.0)
    * Qt6Qml (required version >= 6.5.0)
    * Qt6Widgets (required version >= 6.5.0)
    * KF6ConfigWidgets (required version >= 5.249.0)
    * KF6WidgetsAddons (required version >= 5.249.0)
    * KF6ColorScheme (required version >= 5.249.0)
    * Qt6UiPlugin
    Required to build Qt Designer plugins
    * Qt6

    -- The following features have been disabled:

    * QCH, API documentation in QCH format (for e.g. Qt Assistant, Qt Creator & KDevelop)

    -- Found clang-format version 16
    -- Configuring incomplete, errors occurred!
    FAILED: build.ninja
    /usr/bin/cmake --regenerate-during-build -S/home/chris/kde/src/kiconthemes -B/home/chris/kde/build/kiconthemes
    ninja: error: rebuilding 'build.ninja': subcommand failed

    P.S. Problem resolved following these instructions!!

  • Goal is > 100k

    February 4th, 2024
  • FreeBSD 13.3-BETA1 released

    February 4th, 2024

    The official Release Schedule of 13.3 version

  • KDE Plasma RC2

    February 4th, 2024

  • USMLE invalidation – statistical analysis

    February 1st, 2024

    The following Twitter post explains the science and statistical analysis behind the USMLE compromise by Nepali candidates.

    “If low-scoring examinees are more likely to answer a question correctly than high scorers, it likely means they’re responding to something in the question stem other than what the construct is intended to assess.

    So what you do is look at each examinee’s performance on the compromised items, and compare it to their performance on not-known-to-be-compromised items. It should be the same. But if certain examinees systematically perform better on compromised items – you’ve found a cheater.

    This procedure was first described after the Medical Council of Canada had an exam breach on the MCCQE Part 1 exam in 2004.”

    I’ve gotten DMs asking “How could the USMLE prove they cheated? High scores alone don’t prove that!”

    -and-

    “How do I know my high score won’t be flagged as evidence of cheating just because of where I took the test?”

    Lemme explain how I think these cheaters were caught.

    (🧵) https://t.co/W1iGCzF1bY

    — Bryan Carmody (@jbcarmody) February 1, 2024

  • ECFMG Invalidation of Nepal applicants

    February 1st, 2024

    https://www.usmle.org/usmle-program-statement-notification-invalidated-exam-scores

  • KDE Plasma 6 RC2 this week

    January 29th, 2024
  • The dark side of AI

    January 29th, 2024

    Google Update Reveals AI Will Read All Your Private Messages

    https://www.forbes.com/sites/zakdoffman/2024/01/28/new-details-free-ai-upgrade-for-google-and-samsung-android-users-leaks/?sh=7810358b7a94

  • FreeBSD’s wikipedia page got vandalized

    January 28th, 2024

    An important lesson that indicates that some of the Wikipedia page edits have malicious intent.

  • FreeBSD and Rust

    January 28th, 2024

    Following the steps of the Linux kernel there is an extended discussion regarding the introduction of Rust code also into the FreeBSD base system. The cost of this change would be the doubling of build-times. imp suggested adding an additional step after buildworld for stuff that requires an external toolchain. That would ease the build time pain and the benefit would be the implementation of new tools that were previously unable to exit or making easier code-testing of some base system components.

    Stuff that could only be written in Rust if it were in base

    • ctl-exporter (I started this, but discovered that the CTL stats API is
      unstable, so it can’t live in ports. Instead, I had to do it in C).
      https://github.com/freebsd/freebsd-src/commit/1a7f22d9c211f504f6c48a86401469181a67ec34
    • fusefs tests. Absolutely impossible to do in C. I considered Rust, but went
      with C++ so they could live in base. They are too closely coupled to
      fusefs(5) to live out-of-tree.
      https://github.com/freebsd/freebsd-src/tree/main/tests/sys/fs/fusefs
    • devd. Currently C++, but imp suggested a rewrite.
      https://github.com/freebsd/freebsd-src/tree/main/sbin/devd
    • zfsd. Currently C++, but I’ve long pondered a rewrite. Using Rust would
      make it more testable.
      https://github.com/freebsd/freebsd-src/tree/main/cddl/usr.sbin/zfsd
    • nscd. Currently C, but confusing and with no test coverage. I’ve
      contemplated a rewrite myself, but I don’t want to do it in C.
      https://github.com/freebsd/freebsd-src/tree/main/usr.sbin/nscd
    • The userland portion of the 802.11ac and Lightning stacks. scottl suggested
      that these were good candidates for Rust.
    • freebsd-kpi-r14-0 . https://crates.io/crates/freebsd-kpi-r14-0

    Stuff that can live in ports, but would be nicer in base

    • gstat-rs https://crates.io/crates/gstat
    • geom-exporter (I’ve started this, but haven’t published it)
    • nfs-exporter https://crates.io/crates/freebsd-nfs-exporter
    • virtiofsd-rs . Nobody has yet tried to port it to FreeBSD. But if the
      connection to bhyve(8) is too intimate, it might be hard to do in ports.
      https://gitlab.com/virtio-fs/virtiofsd
    • jail-exporter https://crates.io/crates/jail_exporter
    • Various jail managers have been attempted in Rust. I think these are fine in
      ports, but others like Goran Mekic have opined that they should be moved to
      base instead.
    • musikid’s pjdfstest rewrite. I think it would be great to start using this
      to test the base system’s file systems. If the tests themselves lived in
      base, they would be easier to sync with file system development.
      https://github.com/musikid/pjdfstest
    • pf-rs. I suspect that the API isn’t very stable.
      https://crates.io/crates/pf-rs
    • benchpmc. The pmc counter names changes between releases.
      https://crates.io/crates/benchpmc

    FreeBSD-related applications that are just fine in ports

    • fsx-rs. Unlike pjdfstest, this only tests datapath APIs. Those are usually
      more stable than control path APIs, so I think there’s little to be gained by
      moving this into base. https://crates.io/crates/fsx
    • ztop. It uses ZFS’s kstats sysctl interface, which is pretty stable.
      https://crates.io/crates/ztop
    • iocage-provision https://crates.io/crates/iocage-provision
    • rsblk https://crates.io/crates/rsblk
    • xfuse https://github.com/KhaledEmaraDev/xfuse

    https://forums.freebsd.org/threads/the-case-for-rust-in-the-base-system.92024/

    https://lists.freebsd.org/archives/freebsd-hackers/2024-January/002823.html

    https://wiki.freebsd.org/Rust

  • Nice ! :)

    January 28th, 2024
  • Anki in Wayland – Current status

    January 28th, 2024

    Fractional scaling in Anki yields in blurry fonts. Tried setting the environmental variable to ANKI_WAYLAND=1, in order to “force” Wayland mode.

    Apparently this did not work due to a QT bug that is still unresolved: https://github.com/ankitects/anki/issues/1767, https://github.com/qutebrowser/qutebrowser/issues/6914

    A temporary bypass is setting the env variable QT_QPA_PLATFORM to xcb aka using X11 mode until the bug is fixed.

    P.S.: Starting Anki with QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor works and there is no need to use X11 legacy mode!!

    https://forums.ankiweb.net/t/anki-in-wayland/40361/5

←Previous Page
1 … 102 103 104 105 106 … 132
Next Page→

Blog at WordPress.com.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
 

Loading Comments...
 

    • Subscribe Subscribed
      • /root
      • Already have a WordPress.com account? Log in now.
      • /root
      • Subscribe Subscribed
      • Sign up
      • Log in
      • Report this content
      • View site in Reader
      • Manage subscriptions
      • Collapse this bar