投稿者: user ss

  • Fortran IV G1 compiler

    Fortran IV G1 compiler

    It seems like you’re asking about the “Fortran IV G1 compiler.” Based on historical context, this likely refers to one of IBM’s Fortran IV compilers developed for the System/360 series in the mid-1960s. IBM offered several Fortran IV compilers—named F, G, H, and later others—each distinguished by the amount of memory they required to operate and their optimization levels. The “G” compiler, in particular, was a widely used version, and “G1” might be a specific variant or a misremembered designation.

    To clarify: Fortran IV (often associated with the 1966 standard, Fortran 66) was a significant evolution of the Fortran language, introducing features like logical IF statements and explicit type declarations. The IBM Fortran IV G compiler was designed for the System/360, requiring a modest amount of memory (typically around 64K bytes) compared to the more advanced H compiler. It was less optimized than H but more practical for smaller systems.

    Unfortunately, no Fortran IV G1 compiler (or even G) is readily available today as a standalone tool, especially not for modern systems. These were proprietary IBM products tied to specific hardware like the System/360, and their original distributions are long obsolete. However, here’s how you might approach this:

    1. Modern Compilers for Fortran IV Code: Most contemporary Fortran compilers (e.g., GNU Fortran gfortran, Intel Fortran ifort or ifx, or NAG Fortran) can compile Fortran IV code with minimal adjustments, as the language has maintained a high degree of backward compatibility. For instance:
    • gfortran (part of GCC) supports Fortran 77 and later standards, which encompass Fortran IV features. You’d need to ensure fixed-format source (columns 7–72 for code, column 1 for comments with C or *) and possibly adjust for deprecated constructs like Hollerith constants.
    • Intel Fortran compilers offer a -f66 flag to enforce Fortran 66 semantics, which aligns closely with Fortran IV.
    1. Emulation: If you specifically need the IBM Fortran IV G compiler’s behavior (e.g., for historical accuracy), you’d need an emulator for the System/360, such as Hercules, paired with an original IBM OS like OS/360. The compiler itself would require vintage software archives, which are rare and often inaccessible outside of specialized collections or museums.
    2. Practical Steps: If you have Fortran IV code you want to run:
    • Rename the file with a .f extension (e.g., program.f).
    • Try compiling with gfortran -ffixed-form program.f -o program. The -ffixed-form flag ensures it respects the old card-based layout.
    • Fix any errors (e.g., outdated I/O statements like WRITE (6,10) referencing unit 6 for output might need adjustment depending on the system).

    If “G1” refers to something more specific (e.g., a typo or a different system), could you clarify? For example, was this code intended for a non-IBM platform, or do you have a particular source file in mind? Without additional context, I’m assuming you’re seeking general information or a way to use such a compiler today.

    Given it’s March 4, 2025, no original Fortran IV G1 compiler is in active use, but modern tools can bridge the gap. Let me know if you need help with a specific code example!

  • Why HTML Files Aren’t Directly Rendered as Emails in Teams

    Why HTML Files Aren’t Directly Rendered as Emails in Teams

    It’s important to understand that Microsoft Teams handles HTML content differently depending on how it’s presented. Here’s a breakdown of the situation and how to approach it:
    Why HTML Files Aren’t Directly Rendered as Emails in Teams:

    For viewing the content of a saved HTML file, download it and open it in a web browser.

    Teams is a Collaboration Platform:

    Teams primarily focuses on chat, file sharing, and collaboration. While it integrates with Outlook, it doesn’t replicate the full email client experience within its chat interface.

    Security Concerns:

    Directly rendering arbitrary HTML could pose security risks. Teams has to balance functionality with protection against malicious code.

    Rendering Differences:

    HTML rendering can vary across different applications. Teams might not have the same rendering engine as a dedicated email client.
    How to Approach Viewing HTML Email Content in Teams:

    If the HTML is from an Email Sent to a Teams Channel:

    When an email is sent to a Teams channel, Teams attempts to display the content. However, complex HTML or elements that Teams doesn’t support might not render correctly.

    Sometimes, Teams will display the raw HTML code instead of the rendered version.

    Factors that can affect this are:

    Complex CSS.

    JavaScript.

    External image links that are blocked.

    Malformed HTML.

    Viewing the HTML File:

    If you’ve uploaded an HTML file directly to Teams, it will generally be treated as a file.

    To view it as intended, you’ll likely need to:

    Download the file: Download the .html file from Teams.

    Open in a Web Browser: Open the downloaded file in a web browser (like Chrome, Firefox, or Edge). This will render the HTML as a webpage.

    Outlook Integration:

    For actual email viewing, rely on the Outlook application or Outlook on the web, which are designed for that purpose. Teams integrates with Outlook, so you can access your emails through those applications.
    In summary:

    Teams isn’t designed to be a full-fledged HTML email rendering engine.

    For proper HTML email viewing, use Outlook.

  • パッケージグループの一覧 Rockey Linux @Default

    パッケージグループの一覧 Rockey Linux @Default

    インストールできるEnvironment GroupとGroupの一覧表示

    [user@localhost ~]$ dnf group list
    Last metadata expiration check: 0:01:29 ago on Mon 04 Nov 2024 04:18:17 PM JST.
    Available Environment Groups:
    Server
    Minimal Install
    Workstation
    Custom Operating System
    Virtualization Host
    Installed Environment Groups:
    Server with GUI
    Installed Groups:
    Container Management
    Headless Management
    Available Groups:
    Legacy UNIX Compatibility
    Console Internet Tools
    Development Tools
    .NET Development
    Graphical Administration Tools
    Network Servers
    RPM Development Tools
    Scientific Support
    Security Tools
    Smart Card Support
    System Tools

    InstallされているGroupの一覧を表示する


    [user@localhost ~]$ dnf group list installed
    Last metadata expiration check: 0:02:08 ago on Mon 04 Nov 2024 04:18:17 PM JST.
    Installed Environment Groups:
    Server with GUI
    Installed Groups:
    Container Management
    Headless Management

    InstallされたEnviroment Groupに含まれるGroup

    user@localhost ~]$ sudo dnf group info “Server with GUI”

    Last metadata expiration check: 0:02:20 ago on Mon 04 Nov 2024 04:38:51 PM JST.
    Environment Group: Server with GUI
    Description: An integrated, easy-to-manage server with a graphical interface.

    Mandatory Groups:
    Common NetworkManager submodules
    Container Management
    Core
    Fonts
    GNOME
    Guest Desktop Agents
    Hardware Monitoring Utilities
    Hardware Support
    Headless Management
    Internet Browser
    Multimedia
    Printing Client
    Server product core
    Standard
    base-x

    Optional Groups:
    Basic Web Server
    DNS Name Server
    Debugging Tools
    FTP Server
    File and Storage Server
    Guest Agents
    Infiniband Support
    Mail Server
    Network File System Client
    Network Servers
    Performance Tools
    Remote Desktop Clients
    Remote Management for Linux
    Virtualization Client
    Virtualization Hypervisor
    Virtualization Tools
    Windows File Server

    Otional Groupのインストール方法

    [user@localhost ~]$ sudo dnf groupinstall “Basic Web Server”
    Last metadata expiration check: 0:14:31 ago on Mon 04 Nov 2024 04:38:51 PM JST.
    Dependencies resolved.
    Package Architecture Version Repository Size
    Installing group/module packages:
    httpd x86_64 2.4.57-11.el9_4.1 appstream 44 k
    httpd-manual noarch 2.4.57-11.el9_4.1 appstream 2.2 M
    mod_fcgid x86_64 2.3.9-28.el9 appstream 74 k
    mod_ssl x86_64 1:2.4.57-11.el9_4.1 appstream 108 k
    Installing dependencies:
    apr x86_64 1.7.0-12.el9_3 appstream 122 k
    apr-util x86_64 1.6.1-23.el9 appstream 94 k
    apr-util-bdb x86_64 1.6.1-23.el9 appstream 12 k
    httpd-core x86_64 2.4.57-11.el9_4.1 appstream 1.4 M
    httpd-filesystem noarch 2.4.57-11.el9_4.1 appstream 11 k
    httpd-tools x86_64 2.4.57-11.el9_4.1 appstream 79 k
    rocky-logos-httpd noarch 90.15-2.el9 appstream 24 k
    Installing weak dependencies:
    apr-util-openssl x86_64 1.6.1-23.el9 appstream 14 k
    mod_http2 x86_64 2.0.26-2.el9_4.1 appstream 163 k
    mod_lua x86_64 2.4.57-11.el9_4.1 appstream 58 k
    Installing Groups:
    Basic Web Server
    Transaction Summary
    Install 14 Packages

  • OpenFOAMの計算がSLURMクラスターでどのように動作するか

    OpenFOAMの計算がSLURMクラスターでどのように動作するか


    1. ユーザー操作:
      • ユーザーはSSHを使用してクラスターにログイン
      • OpenFOAMのケースディレクトリとSLURMジョブスクリプトを準備
      • sbatchsrunコマンドでジョブを投入
    2. SLURM管理:
      • SLURMコントローラーがジョブを受け付け
      • ジョブスケジューラーが優先順位と利用可能なリソースを評価
      • 要求されたリソースに基づいて適切な計算ノードを割り当て
    3. 計算プロセス:
      • ノードが割り当てられると、OpenFOAM計算が開始
      • decomposeParで自動的にケースが分割される
      • 各計算ノードが領域の一部を担当
      • MPI(Message Passing Interface)でノード間通信
    4. OpenFOAMワークフロー:
      • decomposePar:領域を並列部分に分割
      • 並列ソルバーが複数ノードで同時実行
      • reconstructPar:結果を単一のソリューションに統合
    5. ストレージシステム:
      • 共有ストレージから入力ファイルを読み込み
      • 結果を共有ストレージに書き込み
      • すべてのノードが同じファイルシステムにアクセス可能

    #!/bin/bash
    #SBATCH --job-name=openfoam_calc
    #SBATCH --nodes=4
    #SBATCH --ntasks-per-node=32
    #SBATCH --time=24:00:00
    #SBATCH --partition=compute
    
    # OpenFOAMモジュールの読み込み
    module load openfoam
    
    # ケースの分割
    decomposePar
    
    # 並列でソルバーを実行
    mpirun simpleFoam -parallel
    
    # 結果の再構築
    reconstructPar

  • Rocky Linuxの異なるデスクトップ環境の違い

    Rocky Linuxの異なるデスクトップ環境の違い

    デスクトップ環境説明リソース使用量
    GNOMEモダンで使いやすく、多機能で洗練されたインターフェース。中〜高
    KDE Plasmaカスタマイズ可能で多機能、視覚的に魅力的なインターフェース。中〜高
    XFCE軽量で高速、古いハードウェアやシンプルなインターフェースを好むユーザーに適している。
    MATEGNOME 2の継続で、従来のデスクトップ体験を提供し、リソース使用量が少ない。低〜中
    LXDE非常に軽量で高速、古いハードウェアやミニマリストな設定に最適。非常に低い
    Cinnamon親しみやすいレイアウトでモダンなデスクトップ環境を提供し、パフォーマンスと美観のバランスが良い。