neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Quick Start Guide — LUCID Toolkit — GPT + Qualtrics Backend Welcome to the backend server powering the LUCID Toolkit — a research infrastructure for running controlled GPT-based chatbot interactions directly inside Qualtrics surveys. This code (Flask backend) serves as a secure proxy to the OpenAI API — allowing each researcher or research team to create their own isolated, privacy-preserving implementation of the LUCID system. ⚠️ Why Is a Separate Server Needed?README 전문 보기 ↗
Welcome to the backend server powering the LUCID Toolkit — a research infrastructure for running controlled GPT-based chatbot interactions directly inside Qualtrics surveys.
This code (Flask backend) serves as a secure proxy to the OpenAI API — allowing each researcher or research team to create their own isolated, privacy-preserving implementation of the LUCID system.
It is not safe to embed an OpenAI API key directly in Qualtrics — whether in JavaScript, Survey Flow, or an HTML element. Survey participants (or anyone inspecting the page) could easily view and copy your key.
The LUCID backend solves this by securely handling GPT requests on your own private server. The API key is never visible to participants. And the best part?
You only need two accounts to get started:
An OpenAI API Key
A GitHub Account
(Optional) A printable version of our detailed setup guide containing all steps with screenshots 📄 Guide (.docx)
If you have all this, you're ready to get started.
To get started, click the following button:
You'll be taken to Vercel.
my-lucid-backend-code). This name will determine your default backend deployment URL that will be used by Qualtrics, so use a name you are comfortable with others (such a reviewers) potentially seeing.OPENAI_API_KEY:
OPENAI_API_KEY value field in Vercel.Visit Your Deployment: Once Vercel shows the deployment is complete ("Congratulations!"), click the image displayed that says in blue text "LUCID Backend Succesfully Deployed!".
Copy the URL: The resulting page you visit should display "LUCID Backend Successfully Deployed!". It will clearly show the exact URL needed for Qualtrics. Click the "Copy Backend URL" button (e.g., https://your-project-name.vercel.app/lucid). Keep this address handy for the Qualtrics setup.
Download your .QSF file from this repository:
LUCID_Qualtrics_Template_1_-One_Group_Design.qsf - A single condition design (e.g., for conducting an interview using the same chatbot for all participants)
LUCID_Qualtrics_Template_2_-Two_Group_Between_Subjects_Experiment.qsf - A 2-Group between subjects design (e.g., for conducting an experiment that manipulates chatbot behavior)
Garvey, Aaron M. and Simon J. Blanchard, (2025) "Generative AI as a Research Confederate: The LUCID Methodological Framework and Toolkit for Human-AI Interactions Research," MSI Working Paper. paper@ssrn
Blanchard, S. J., Duani, N., Garvey, A. M., Netzer, O., & Tae Oh, T. (2025). New Tools, New Rules: A Practical Guide to Effective and Responsible Generative AI Use for Surveys and Experiments in Research. Journal of Marketing, 89(6), 119-139. paper@Journal of Marketing
The code contents of this git repository are available for non-commercial use under Creative Commons BY-NC-SA (https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode.en).