louis714
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    ## 專題【財神360】每週進度 <details> <summary>114下第一週及第二週 2/18-3/4</summary> 未來兩週的規劃與分工: **1. Python 開發** 任務:熟悉python及OpenAI Playground 負責人:章晏、靖茨、育任 **任務詳細分工:** * 育任:熟悉 OpenAI Playground,並說明功能應用 * 靖茨、章晏:了解學長寫的程式,嘗試模仿並將文字匯出成報表 **示例:** 輸入:2/25 早餐 50 元 輸出: | 時間 | 類別 | 金額 | | -------- | -------- | -------- | | 2025.02.25 | 食 | 50元 | 成果展示(嘗試模仿並將文字匯出成報表): 檔案放至於雲端硬碟python組資料夾中 https://drive.google.com/drive/folders/17ce16d_I0EvFkyU0dTXKpEMKhc-9UIT9?usp=drive_link OpenAI playground展示:(下週會口頭說明) * GPT模型INPUT ![image](https://hackmd.io/_uploads/HylchXVj1l.png) * 模型回覆OUTPUT ![image](https://hackmd.io/_uploads/Hkd237Eokl.png) * 手機的介面(未完成) ![image](https://hackmd.io/_uploads/ry7qkEVi1e.png) --- **2.Apex** • 任務:匯入對帳單的畫面 • 負責人:寶文、珮婕、沛芝。 任務一詳細敘述 1.建立儲存對帳單的資料表 ![{317DE036-C5BF-4518-B67B-931F2F42D8B4}](https://hackmd.io/_uploads/BknXYFVjJx.png) 2.做出匯入檔案畫面 ![圖片_2025-03-04_150054448](https://hackmd.io/_uploads/r1ZESmNi1x.png) 3.將對帳單的pdf檔匯入至Apex的介面。 https://drive.google.com/drive/folders/1S2yGyLcTkSS7moZXLRqiiwkQJzzcMUYj?usp=sharing --- </details> <details> <summary>114下第三週及第四週 3/4-3/18</summary> **1. Python 開發** * 任務詳細敘述: 1.弄懂學長streamlit程式,熟悉streamlit的使用功能,製作一個example介面與功能 2.找出程式中開始呼叫Chat LLM的地方,確認是哪段程式被呼叫,讀取該程式的名稱並理解用途 **2. Apex 開發** * 任務詳細敘述 1.用真的對帳單轉出csv檔 2.建立儲存表格 3.做出匯入功能 </details> <details> <summary>114下第五週及第六週 3/18-4/1</summary> **1. Python 開發** * 任務詳細敘述: 1.依照userstory在streamlit雛形對話框以及做出UI 2.處理後端llm要可以執行userstory功能 * 遇到問題以及解決方法: 1. 後端llm無法結合我們自己做的streamlit (本來想用學長的core,但無法成功結合) 2. 歷史紀錄無法顯示出來 **2. Apex 開發** * 任務詳細敘述 1.確定表格名稱 2.觀看影片並學習製作匯入對帳單 </details> <details> <summary>114下第六週及第七週 4/1-4/15</summary> **1. Python 開發** * 任務詳細敘述: 1.建立一個假的 Chatbot,僅回答固定問題 事先設定問題與對應的答案,例如: A 問 → A 答 B 問 → B 答 * 遇到問題以及解決方法: 1. 使用 if-else 或 JSON 格式來儲存問答對應關係。 模擬 LLM 函數簽名,參考學長的 core.py **2. Apex 開發** * 任務詳細敘述 1.命名表格名稱與資料型態 2.日期搜尋功能及畫面 3.編輯功能及畫面 4.製作消費紀錄查詢介面 5.製作消費紀錄的折線圖及圓餅圖 </details> <details> <summary>114下第八週及第九週 4/15-4/29</summary> **1. Python 開發** * 任務詳細敘述: 1.將結果輸出成JSON格式 2.加上更多提示詞,讓記帳結果更準確 **2. Apex 開發** * 任務詳細敘述 1.使用 Classic Report 呈現卡片 2.增加折線圖資料 </details> <details> <summary>114下第十週及第十一週 4/29-5/13</summary> **1. Python 開發** * 任務詳細敘述: 1.報告python如何發出http的post請求,資料轉.josn,送資料至APEX 2.故事地圖更新 3.新增「支付方式與備註」格式 4.做出收入類別 5.額外處理(有時間的話) 5-1.極端情境輸入 5-2.訂定測試案例規則,確認開發結束 5-3.批次處理 **2. Apex 開發** * 任務詳細敘述 1.篩選支付方式再呈現記帳資料 2.整理並報告折線圖的日期 3.記帳資料、存放記帳資料的table要更新(增加支出的類別) </details> <details> <summary>114下第十四週及第十五週 5/27-6/10</summary> **1. Python 開發** * 任務詳細敘述: 1.報告python如何發出http的post請求,資料轉.josn,送資料至APEX 2.將資料傳送至 APEX 的功能整合進 Streamlit 介面,實現使用者操作與資料上傳的接軌。 </details> <details> <summary>114下第十六週及第十七週 6/10-6/24</summary> **1. Python 開發** * 任務詳細敘述: 1.修改core.py檔 把人工處理的部分改成都交給llm處理 2.修改user story 預算部分 描述出使用者是如何使用查詢預算的介面 3.撈取apex預算資料 讓使用者能夠在介面上看到還剩下多少預算 **2. Apex 開發** * 任務詳細敘述 1.增加預算前端及後端的故事內容 2.跟python討論表格內容 3.討論UI介面要呈現什麼內容並製作 4.製作預算需要使用的假資料 Apex遇到的問題 1.我們後端apex是要使用get還是post? 我們在做後端的時候有發現到,使用者在設置預算資料的時候,這裡我們apex是要跟python抓取資料,然後我們再回傳給python,還有一個不確定的是python是不是也要向我們apex抓取資料,然後再回傳給我們apex 因為我們各自查gpt的時候,gpt給我們不一樣的方法是使用get跟post,所以我們現在有點不確定是要使用哪一個回傳方式,還是兩個都要做 2.如果是用get的話要怎麼做? 是要回傳什麼東西呢? A:回傳使用者設置的預算資料 回傳 sql 查詢結果嗎? A:不是~ 是那個 User Story 要使用的? A:後端預算的user story,python 向我們抓取資料,我們apex再回傳 Apex開會整理 1.需求要確定,先把預算的使用者故事相關功能、作業流程跟畫面模擬出來 2.第一個故事是在後端設預算、第二個故事是在手機上知道預算的餘額 3.Get需要使用select,子句分別有where、group by、sum </details> <details> <summary>114下第十六週及第十七週 7/1-7/8</summary> **1. Python 開發** * 任務詳細敘述:

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully