@research-copilot/plugin 1.1.17 → 1.1.19

package/dist/skills/research-paper-writing/references/examples/method/module-motivation-patterns.md

@@ -0,0 +1,15 @@
+# Module Motivation Writing Patterns
+
+
+`Module motivation is usually problem-driven: because a problem exists, we design xx to solve it.`
+
+Typical opening sentences:
+
+1. `A remaining problem/challenge is ...`
+2. `However, we ...`
+3. `Previous methods have difficulty in ...`
+
+Usage note:
+
+1. State the specific failure before introducing the module.
+2. Keep motivation independent from implementation details.

package/dist/skills/research-paper-writing/references/examples/method/module-triad-neural-body.md

@@ -0,0 +1,19 @@
+# Module Triad Example (Neural Body)
+
+`Use Neural Body to understand the three elements of a module: design, motivation, and technical advantages.`
+
+Local source references:
+
+1. Annotated figure showing motivation/design/advantages split.
+3. Text-converted annotation notes: `references/examples/method/neural-body-annotated-figure-text.md`
+
+Triad mapping template:
+
+1. Module design: what representation/network is built and how forward process runs.
+2. Motivation: what unresolved challenge requires this module.
+3. Technical advantages: why this module performs better than alternatives.
+
+Direct usage:
+
+1. Read `neural-body-annotated-figure-text.md` to map each paragraph to one triad element.
+2. Rebuild your own Method subsection with the same triad order.

package/dist/skills/research-paper-writing/references/examples/method/neural-body-annotated-figure-text.md

@@ -0,0 +1,66 @@
+# Neural Body Annotated Figure (Text Conversion)
+
+This file converts the annotated Neural Body figure into reusable writing notes.
+
+## Purpose
+
+Use this mapping to understand how one Method section can explicitly separate:
+
+1. Module motivation
+2. Module design (data structure)
+3. Module design (forward process)
+4. Technical advantages
+
+## Block-by-Block Mapping
+
+### Section 3.1: Structured Latent Codes
+
+1. **Module design (data structure)**
+- The paragraph defines structured latent codes anchored to the deformable human model (SMPL).
+- It explains what is constructed (latent codes + their anchor positions + frame-dependent transformation by pose).
+
+2. **Technical advantages**
+- The paragraph explains why this design works better: dynamic-human representation and cross-frame integration of observations.
+- It highlights why anchoring codes to deformable geometry is beneficial.
+
+### Section 3.2: Code Diffusion
+
+1. **Motivation of this module**
+- The paragraph states the remaining problem: direct interpolation of sparse structured codes leads to near-zero vectors at many 3D points.
+- This motivates diffusion from surface codes to nearby 3D space.
+
+2. **Module design (forward process)**
+- The paragraph explains the execution pipeline: build sparse latent volumes, run sparse convolutions, interpolate latent codes at query points, and feed codes to prediction networks.
+- This is a canonical input -> steps -> output module description.
+
+### Section 3.3: Density and Color Regression
+
+1. **Module design (forward process) for density model**
+- The density paragraph defines how density is regressed from latent code and frame condition.
+
+2. **Module design (data structure) for color model**
+- The color paragraph introduces required inputs/embeddings (latent code, view direction, spatial location, temporal embedding).
+
+3. **Module design (forward process) for color model**
+- The next paragraph describes how those inputs are encoded and passed into the color MLP for final color prediction.
+
+### Section 3.4: Volume Rendering
+
+1. **Module design (forward process)**
+- The paragraph describes ray sampling and volume integration to render image outputs from predicted density/color fields.
+
+## Reusable Writing Pattern from This Figure
+
+For each module subsection, follow this order:
+
+1. `Motivation`: state unresolved challenge and technical reason.
+2. `Design-1`: define structure/representation/network.
+3. `Design-2`: describe forward process in execution order.
+4. `Advantage`: explain why this module improves over alternatives.
+
+## Suggested Paragraph Starters
+
+1. Motivation: `A remaining challenge is ...`
+2. Data structure design: `We represent ... with ...`
+3. Forward process: `Given [input], we first ... then ... finally ...`
+4. Technical advantage: `Compared with previous methods, this design ... because ...`

package/dist/skills/research-paper-writing/references/examples/method/overview-template.md

@@ -0,0 +1,30 @@
+# Method Overview Template
+
+
+`Overview usually includes setting, core contribution, optional figure pointer, and subsection map.`
+
+```latex
+% Overview
+% One or two sentences for setting
+%% Example 1: Given a sparse multi-view video of a performer, our task is to generate a free-viewpoint video of the performer.
+%% Example 2: Given an image, the task of pose estimation is to detect objects and estimate their orientations and translations in the 3D space.
+
+% One or two sentences for core contribution
+%% Example 1: We build upon prior work for static scenes [46], to which we add the notion of time, and estimate 3D motion by explicitly modeling forward and backward scene flow as dense 3D vector fields.
+%% Example 2: Inspired by [21, 25], we perform object segmentation by deforming an initial contour to match object boundary.
+%% Example 3: Inspired by recent methods [29, 30, 36], we estimate the object pose using a two-stage pipeline: we first detect 2D object keypoints using CNNs and then compute 6D pose parameters using the PnP algorithm. Our innovation is in a new representation for 2D object keypoints as well as a modified PnP algorithm for pose estimation.
+
+% If pipeline/framework is novel, point to figure
+%% Example: The overview of the proposed model is illustrated in Figure 3.
+
+% Explain what Section 3.1 covers
+%% Example 1: Neural Body starts from a set of structured latent codes attached to the surface of a deformable human model (Section 3.1).
+%% Example 2: In this section, we first describe how to model 3D scenes with MLP maps (Section 3.1).
+
+% Explain what Section 3.2 covers
+%% Example 1: The latent code at any location around the surface can be obtained with a code diffusion process (Section 3.2) and then decoded to density and color values by neural networks (Section 3.3).
+%% Example 2: Then, Section 3.2 discusses how to represent volumetric videos with dynamic MLP maps.
+
+% Explain what Section 3.3 covers
+%% Example 3: Finally, we introduce some strategies to speed up the rendering process (Section 3.3).
+```

package/dist/skills/research-paper-writing/references/examples/method/pre-writing-questions.md

@@ -0,0 +1,17 @@
+# Method Pre-Writing Questions
+
+
+`Before writing Method, answer: (1) what modules exist, and (2) for each module, what is its workflow, why is it needed, and why does it work.`
+
+```text
+Questions:
+(1) What modules are in the method?
+(2) For each module, answer three questions:
+    - What is this module's workflow?
+    - Why do we need this module?
+    - Why does this module work?
+```
+
+Recommended action:
+
+1. Organize answers in a mind map or table before writing paragraphs.

package/dist/skills/research-paper-writing/references/examples/method/section-skeleton.md

@@ -0,0 +1,9 @@
+# Method Section Skeleton
+
+```latex
+\section{Method}
+% Overview
+% Section 3.1
+% Section 3.2
+% Section 3.3
+```

package/dist/skills/research-paper-writing/references/examples/method-examples.md

@@ -0,0 +1,24 @@
+# Method Examples Index
+
+All method example cites should point to the local files below.
+
+## A. Planning and Writing Workflow
+
+1. Pre-writing questions: `references/examples/method/pre-writing-questions.md`
+
+## B. Module Triad and Module-Level Writing
+
+1. Module triad (Neural Body): `references/examples/method/module-triad-neural-body.md`
+2. Neural Body figure text conversion: `references/examples/method/neural-body-annotated-figure-text.md`
+3. Module design (Instant-NGP): `references/examples/method/module-design-instant-ngp.md`
+4. Module motivation patterns: `references/examples/method/module-motivation-patterns.md`
+
+## C. Section-Level Templates
+
+1. Method section skeleton: `references/examples/method/section-skeleton.md`
+2. Overview template: `references/examples/method/overview-template.md`
+3. Example of the three elements: `references/examples/method/example-of-the-three-elements.md`
+
+## D. Clarity and Troubleshooting
+
+1. Common issues note: `references/examples/method/method-writing-common-issues-note.md`

package/dist/skills/research-paper-writing/references/experiments.md

@@ -0,0 +1,102 @@
+# Experiments Writing Guide
+
+## Goal
+
+Convince reviewers with complete evidence on effectiveness, causality, and practical value.
+
+## Three Core Questions
+
+1. Is the method better than strong baselines?
+   - Run comparison experiments against strong and recent baselines.
+   - Report standard metrics on the main benchmark(s).
+   - Include SOTA or strongest public methods, not only weak baselines.
+   - Keep protocol fair (same data split, preprocessing, and evaluation settings).
+2. Which modules/design choices make the gain?
+   - Run ablation studies for each key module/design choice.
+   - Use remove/replace/disable variants and report delta to full model.
+   - Include component interaction ablations when modules are coupled.
+3. How far can the method generalize under harder settings?
+   - Run demos/evaluations on harder or out-of-distribution settings.
+   - Add stress-test scenarios (more complex scenes, rarer cases, noisier inputs, or stricter constraints).
+   - Report both gains and failure modes to show realistic boundaries.
+
+## Experiment Planning
+
+```mermaid
+flowchart TB
+    A["Key Paper Claims"] --> B["What Contributions Are Claimed?"]
+    B --> C1["Contribution 1"]
+    B --> C2["Contribution 2"]
+    B --> C3["Contribution 3"]
+    C1 --> D1["Validation Experiment 1"]
+    C2 --> D2["Validation Experiment 2"]
+    C3 --> D3["Validation Experiment 3"]
+
+    E["Method Pipeline Figure"] --> F["What Modules and Parameters Matter?"]
+    F --> G1["Technical Module 1"]
+    F --> G2["Technical Module 2"]
+    F --> G3["Key Parameter 1"]
+    F --> G4["Key Parameter 2"]
+    G1 --> H1["Ablation Study 1"]
+    G2 --> H2["Ablation Study 2"]
+    G3 --> H3["Ablation Study 3"]
+    G4 --> H4["Ablation Study 4"]
+```
+
+## Experiment Section Decomposition
+
+```mermaid
+flowchart TB
+    S1["Experimental Setup"] --> S2["Validation Experiment 1"]
+    S2 --> S3["Validation Experiment 2"]
+    S3 --> S4["Ablation Studies"]
+```
+
+## Figure/Table Writing Rules
+
+`Good tables are part of experiment communication quality, not decoration.`
+
+1. Figure captions and table captions are equally important in the writing quality of Experiments.
+
+### Hard rules
+
+1. Put caption above the table.
+2. Avoid vertical lines (`|`) in tabular columns.
+3. Do not use double rules or dense `\hline` stacks.
+4. Use `booktabs` style (`\toprule`, `\midrule`, `\bottomrule`) for clean structure.
+5. Use as few horizontal rules as possible; lines should separate groups, not every row.
+6. Highlight key numbers (best/second-best or target rows) with subtle color emphasis.
+
+### Readability rules from review practice
+
+1. Label metric direction in column headers (for example `PSNR ↑`, `LPIPS ↓`).
+2. Add units when needed so values are interpretable without guessing.
+3. Align text columns left; keep numeric columns consistently aligned.
+4. Keep numeric precision consistent (same decimal places within a metric column).
+5. Group multi-dataset or multi-setting results using `\multicolumn` + `\cmidrule`, not vertical separators.
+6. One table, one message: do not mix unrelated results in a single table.
+7. If rows represent different attributes/ablations, encode that explicitly in row names or attribute columns.
+8. Keep caption focused on setting/protocol/notation, not long discussion.
+9. If there is little detail to explain, use one concise sentence to summarize the main result.
+10. For single-column figures/tables in two-column papers, prefer placing them in the right column when layout allows, so readers can enter the page from the left-top text without breaking reading flow.
+
+### Minimal LaTeX checklist
+
+1. Add packages in preamble: `\usepackage{booktabs}`, `\usepackage{colortbl,xcolor}` (and optionally `\usepackage{siunitx}` for decimal alignment).
+2. Replace `\hline`-heavy style with `\toprule/\midrule/\bottomrule`.
+3. Put `\caption{...}` before `\label{...}` and keep caption above.
+4. Use restrained highlighting; never color too many cells.
+
+## Recommended Ablation Package
+
+1. One core ablation table for all major contributions.
+2. Several focused mini-ablations for module-level design choices.
+3. Matching qualitative visual results for each important ablation.
+
+## Experimental Rigor Checklist
+
+1. Are baselines recent and relevant?
+2. Are metrics sufficient and standard for this task?
+3. Is ablation tied to every key design claim?
+4. Are claims in Abstract/Introduction supported by reported numbers?
+5. Are limitations of evaluation scope explicitly stated?