ai-research-survey

Systematic scan of agentic development research. What's signal, what's noise.
git clone https://git.shiptheloop.com/ai-research-survey.git
Log | Files | Refs

scan.json (29353B)


      1 {
      2   "paper": {
      3     "title": "Training LLMs for Generating IEC 61131-3 Structured Text with Online Feedback",
      4     "authors": [
      5       "Aaron Haag",
      6       "Bertram Fuchs",
      7       "Altay Kacan",
      8       "Oliver Lohse"
      9     ],
     10     "year": 2024,
     11     "venue": "2025 IEEE/ACM International Workshop on Large Language Models for Code (LLM4Code)",
     12     "arxiv_id": "2410.22159",
     13     "doi": "10.1109/LLM4Code66737.2025.00013"
     14   },
     15   "scan_version": 2,
     16   "active_modules": ["experimental_rigor", "data_leakage"],
     17   "methodology_tags": ["benchmark-eval"],
     18   "key_findings": "The paper proposes an iterative online DPO approach combining compiler feedback and LLM-based semantic expert feedback to fine-tune Phi-3-medium-instruct (14B) for IEC 61131-3 Structured Text code generation. Starting from a 7% baseline compilation rate, the method achieves ~70% compilation rate and ~45% semantic correctness after 9 DPO iterations, outperforming GPT-3.5 Turbo (40% compilation). Performance plateaus after approximately iteration 2, and the joint compilation + semantic correctness rate reaches ~39%.",
     19   "checklist": {
     20     "artifacts": {
     21       "code_released": {
     22         "applies": true,
     23         "answer": false,
     24         "justification": "No repository URL, GitHub link, or code archive is mentioned anywhere in the paper."
     25       },
     26       "data_released": {
     27         "applies": true,
     28         "answer": false,
     29         "justification": "The paper uses APPS (public) and OSCAT (public) as source datasets, but the converted ST code dataset (~2000 samples transpiled from Python via GPT-4) and the evaluation datasets are not released."
     30       },
     31       "environment_specified": {
     32         "applies": true,
     33         "answer": false,
     34         "justification": "The paper mentions 'two NVIDIA GTX A6000 GPUs, providing a total of 96GB of memory' and that Phi-3 14B was used without quantization, but provides no requirements.txt, library versions, or detailed environment specification sufficient to recreate the setup."
     35       },
     36       "reproduction_instructions": {
     37         "applies": true,
     38         "answer": false,
     39         "justification": "No step-by-step reproduction instructions are provided. Algorithm 1 gives a high-level pseudocode but lacks the specific details needed to replicate the experiments."
     40       }
     41     },
     42     "statistical_methodology": {
     43       "confidence_intervals_or_error_bars": {
     44         "applies": true,
     45         "answer": false,
     46         "justification": "Fig. 3 shows only point estimates for compilation rate, semantic correctness, and joint rate across iterations. No error bars, confidence intervals, or uncertainty measures are reported."
     47       },
     48       "significance_tests": {
     49         "applies": true,
     50         "answer": false,
     51         "justification": "The paper claims their method outperforms GPT-3.5 and baseline models based solely on comparing point estimates (e.g., 70% vs 40% compilation rate) without any statistical significance tests."
     52       },
     53       "effect_sizes_reported": {
     54         "applies": true,
     55         "answer": true,
     56         "justification": "The paper reports improvements with baseline context: 'compilation success rate of around 70%, a substantial increase from the baseline's 7%' and comparison to GPT-3.5 at 40%. This provides sufficient context to assess the magnitude of improvement."
     57       },
     58       "sample_size_justified": {
     59         "applies": true,
     60         "answer": false,
     61         "justification": "The evaluation dataset is 200 intents (100 OSCAT + 100 converted APPS) with no justification for this size or discussion of whether it is sufficient for the claims made."
     62       },
     63       "variance_reported": {
     64         "applies": true,
     65         "answer": false,
     66         "justification": "No variance, standard deviation, or spread measures are reported. Results appear to be from single runs with no indication of result stability across different random seeds or initializations."
     67       }
     68     },
     69     "evaluation_design": {
     70       "baselines_included": {
     71         "applies": true,
     72         "answer": true,
     73         "justification": "The paper compares against the base model θ (Phi-3 without fine-tuning), the SFT model θsft, and GPT-3.5 Turbo as an external baseline, shown in Fig. 3."
     74       },
     75       "baselines_contemporary": {
     76         "applies": true,
     77         "answer": false,
     78         "justification": "The only external baseline is GPT-3.5 Turbo. In 2024, GPT-4, Claude, CodeLlama, DeepSeek-Coder, and other code-specialized models exist and would be more competitive baselines. GPT-4 is used only as an evaluator, not as a code generation baseline."
     79       },
     80       "ablation_study": {
     81         "applies": true,
     82         "answer": false,
     83         "justification": "The method has two feedback components (compiler feedback and LLM semantic expert) but no ablation study isolates their individual contributions. There is no experiment showing DPO with only compiler feedback or only LLM feedback."
     84       },
     85       "multiple_metrics": {
     86         "applies": true,
     87         "answer": true,
     88         "justification": "Three metrics are defined and reported: compilation rate (Pc), semantic correctness rate (Ps), and joint compilation + semantic correctness rate (Pj), as described in Section IV.A."
     89       },
     90       "human_evaluation": {
     91         "applies": true,
     92         "answer": false,
     93         "justification": "Semantic evaluation is performed entirely by GPT-4 (gpt-4-1106-preview). No human evaluation of generated code is included. For a domain-specific code generation task targeting industrial automation, human expert evaluation of code quality would be highly relevant."
     94       },
     95       "held_out_test_set": {
     96         "applies": true,
     97         "answer": false,
     98         "justification": "Table I specifies evaluation on '100 OSCAT, 100 converted APPS intents' separate from training data, but there is no explicit statement that these are disjoint from the DPO instruction set (also drawn from OSCAT and APPS). The held-out separation is not clearly documented."
     99       },
    100       "per_category_breakdown": {
    101         "applies": true,
    102         "answer": false,
    103         "justification": "Results are reported only as aggregate metrics (Pc, Ps, Pj) across all 200 evaluation intents. No breakdown by OSCAT vs APPS, by task difficulty, or by problem category is provided."
    104       },
    105       "failure_cases_discussed": {
    106         "applies": true,
    107         "answer": false,
    108         "justification": "No specific failure cases or examples of generated code that fails are shown or analyzed. The discussion mentions generic challenges ('complex algorithms', 'edge cases') but provides no concrete failure examples."
    109       },
    110       "negative_results_reported": {
    111         "applies": true,
    112         "answer": false,
    113         "justification": "All experiments show monotonic improvement. The paper notes performance 'plateaus' after iteration 2 but does not report any configurations, approaches, or design choices that failed or hurt performance."
    114       }
    115     },
    116     "claims_and_evidence": {
    117       "abstract_claims_supported": {
    118         "applies": true,
    119         "answer": false,
    120         "justification": "The abstract claims the framework 'outperforms state-of-the-art models' (plural), but results only compare against GPT-3.5 Turbo. Calling GPT-3.5 'state-of-the-art' in 2024 when GPT-4 and other stronger models exist is misleading. The abstract also claims the approach is 'highly suitable for industrial automation applications' with no real-world deployment evidence."
    121       },
    122       "causal_claims_justified": {
    123         "applies": true,
    124         "answer": false,
    125         "justification": "The paper claims 'The integration of the compiler feedback and the LLM expert...leads to better results' (causal language) but provides no ablation separating the effects of each component. Without isolating variables, the causal attribution is unjustified."
    126       },
    127       "generalization_bounded": {
    128         "applies": true,
    129         "answer": false,
    130         "justification": "While the title appropriately scopes to IEC 61131-3 ST, the conclusion claims the approach 'pav[es] the way for total automation of industry' — a claim far beyond what generating ST code on 200 test intents could support."
    131       },
    132       "alternative_explanations_discussed": {
    133         "applies": true,
    134         "answer": false,
    135         "justification": "No alternative explanations are discussed. For instance, the improvements could stem from increased exposure to code patterns during iterative generation rather than the DPO training signal, or the GPT-3.5 semantic expert could introduce systematic biases. None of these alternatives are considered."
    136       },
    137       "proxy_outcome_distinction": {
    138         "applies": true,
    139         "answer": false,
    140         "justification": "The paper measures compilation rate and GPT-4-judged semantic correctness, then frames these as evidence the code is suitable for 'industrial automation applications.' The gap between GPT-4 judgment and actual functional correctness in PLC systems is not acknowledged. No unit tests, simulation, or hardware validation is performed."
    141       }
    142     },
    143     "setup_transparency": {
    144       "model_versions_specified": {
    145         "applies": true,
    146         "answer": true,
    147         "justification": "Table I specifies 'Phi-3-medium-instruct LLM' as the base model. The semantic expert is 'gpt-3.5-turbo-1106' and the evaluator is 'gpt-4-1106-preview' — both include version/snapshot identifiers."
    148       },
    149       "prompts_provided": {
    150         "applies": true,
    151         "answer": true,
    152         "justification": "Figure 2 provides the full expert prompt used for semantic evaluation, including system and user message structure with the specific formatting instructions."
    153       },
    154       "hyperparameters_reported": {
    155         "applies": true,
    156         "answer": false,
    157         "justification": "Table I reports some experimental parameters (T=15 code responses, I=9 iterations, dataset sizes) but omits critical hyperparameters: learning rate, LoRA rank/alpha, batch size, temperature for code generation, DPO beta parameter, and other fine-tuning settings."
    158       },
    159       "scaffolding_described": {
    160         "applies": false,
    161         "answer": false,
    162         "justification": "No agentic scaffolding is used. The system is a training pipeline (SFT + iterative DPO), not an agent-based system."
    163       },
    164       "data_preprocessing_documented": {
    165         "applies": true,
    166         "answer": false,
    167         "justification": "The paper states implementations were 'transpiled from Python to ST codes using GPT-4, with filtering applied to exclude examples that were either too complex algorithmically or too specific to Python.' The filtering criteria are vague — 'too complex' and 'too specific to Python' are not operationalized."
    168       }
    169     },
    170     "limitations_and_scope": {
    171       "limitations_section_present": {
    172         "applies": true,
    173         "answer": false,
    174         "justification": "There is no dedicated Limitations or Threats to Validity section. Some limitations are discussed within the Results and Discussion section (IV.D) but they are framed as future work directions rather than explicit limitations of the current study."
    175       },
    176       "threats_to_validity_specific": {
    177         "applies": true,
    178         "answer": false,
    179         "justification": "The discussion mentions LoRA's 'reduced parameter count may limit the model's ability' and 'the model relies on patterns learned from training data, which may not always cover edge cases.' These are framed as future improvement areas rather than threats to the validity of the current results."
    180       },
    181       "scope_boundaries_stated": {
    182         "applies": true,
    183         "answer": false,
    184         "justification": "The paper states 'the present work considers only PLC programming in the ST language' but the conclusion contradicts this by claiming the approach 'pav[es] the way for total automation of industry.' No explicit statement of what the results do NOT show."
    185       }
    186     },
    187     "data_integrity": {
    188       "raw_data_available": {
    189         "applies": true,
    190         "answer": false,
    191         "justification": "Neither the converted ST training dataset, the preference datasets generated during DPO iterations, nor the evaluation data are released for independent verification."
    192       },
    193       "data_collection_described": {
    194         "applies": true,
    195         "answer": false,
    196         "justification": "The conversion process from APPS to ST via GPT-4 is described at a high level, but the filtering criteria ('too complex algorithmically or too specific to Python') are not operationalized. How the ~2000 resulting samples were validated or quality-checked is not described."
    197       },
    198       "recruitment_methods_described": {
    199         "applies": false,
    200         "answer": false,
    201         "justification": "No human participants. Data sources are standard datasets (APPS, OSCAT)."
    202       },
    203       "data_pipeline_documented": {
    204         "applies": true,
    205         "answer": false,
    206         "justification": "The paper states the conversion 'resulted in ca. 2000 ST code samples' from APPS, then splits these across SFT (1000), DPO intents (900), and evaluation (100), plus OSCAT splits. But 'ca. 2000' is imprecise, the split methodology is not explained, and how filtering reduced the original APPS dataset to ~2000 is not documented with counts."
    207       }
    208     },
    209     "conflicts_of_interest": {
    210       "funding_disclosed": {
    211         "applies": true,
    212         "answer": false,
    213         "justification": "No funding source or acknowledgments section is present in the paper. The work is conducted at Siemens Technology Department but no explicit funding statement is made."
    214       },
    215       "affiliations_disclosed": {
    216         "applies": true,
    217         "answer": true,
    218         "justification": "All four authors are disclosed as being from 'Siemens Technology Department, Munich, Germany' with Siemens email addresses."
    219       },
    220       "funder_independent_of_outcome": {
    221         "applies": true,
    222         "answer": false,
    223         "justification": "All authors are Siemens employees. Siemens manufactures PLCs and would benefit commercially from improved PLC code generation tools. The employer/implicit funder has a direct financial interest in positive outcomes."
    224       },
    225       "financial_interests_declared": {
    226         "applies": true,
    227         "answer": false,
    228         "justification": "No competing interests or financial interests statement is included. Given all authors work for Siemens (a PLC manufacturer), disclosure of financial interests would be appropriate."
    229       }
    230     },
    231     "contamination": {
    232       "training_cutoff_stated": {
    233         "applies": true,
    234         "answer": false,
    235         "justification": "No training data cutoff date is stated for Phi-3-medium-instruct, GPT-3.5-turbo-1106, or GPT-4-1106-preview. This is important since the evaluation uses APPS and OSCAT data that could be in the models' training sets."
    236       },
    237       "train_test_overlap_discussed": {
    238         "applies": true,
    239         "answer": false,
    240         "justification": "APPS was published in 2021 and OSCAT is publicly available. Phi-3 could have been trained on both. The paper does not discuss whether the base model has prior knowledge of these datasets before fine-tuning."
    241       },
    242       "benchmark_contamination_addressed": {
    243         "applies": true,
    244         "answer": false,
    245         "justification": "APPS examples were published in 2021, well before Phi-3's training. The evaluation intents derived from APPS could have been seen during Phi-3's pre-training. This contamination risk is not addressed."
    246       }
    247     },
    248     "human_studies": {
    249       "pre_registered": {
    250         "applies": false,
    251         "answer": false,
    252         "justification": "No human participants in this study."
    253       },
    254       "irb_or_ethics_approval": {
    255         "applies": false,
    256         "answer": false,
    257         "justification": "No human participants in this study."
    258       },
    259       "demographics_reported": {
    260         "applies": false,
    261         "answer": false,
    262         "justification": "No human participants in this study."
    263       },
    264       "inclusion_exclusion_criteria": {
    265         "applies": false,
    266         "answer": false,
    267         "justification": "No human participants in this study."
    268       },
    269       "randomization_described": {
    270         "applies": false,
    271         "answer": false,
    272         "justification": "No human participants in this study."
    273       },
    274       "blinding_described": {
    275         "applies": false,
    276         "answer": false,
    277         "justification": "No human participants in this study."
    278       },
    279       "attrition_reported": {
    280         "applies": false,
    281         "answer": false,
    282         "justification": "No human participants in this study."
    283       }
    284     },
    285     "cost_and_practicality": {
    286       "inference_cost_reported": {
    287         "applies": true,
    288         "answer": false,
    289         "justification": "No inference cost, API costs (for GPT-3.5/GPT-4 queries during training and evaluation), or per-example generation time is reported. The method generates T=15 samples per intent over I=9 iterations, which incurs substantial cost not quantified."
    290       },
    291       "compute_budget_stated": {
    292         "applies": true,
    293         "answer": false,
    294         "justification": "The paper mentions 'two NVIDIA GTX A6000 GPUs, providing a total of 96GB of memory' but does not report training time, total GPU hours, API costs for GPT-3.5 and GPT-4, or total computational budget."
    295       }
    296     },
    297     "experimental_rigor": {
    298       "seed_sensitivity_reported": {
    299         "applies": true,
    300         "answer": false,
    301         "justification": "No mention of random seeds. Results appear to be from a single training run with no seed sensitivity analysis."
    302       },
    303       "number_of_runs_stated": {
    304         "applies": true,
    305         "answer": false,
    306         "justification": "The paper does not state how many experimental runs produced the reported results. It appears to be a single run through 9 DPO iterations."
    307       },
    308       "hyperparameter_search_budget": {
    309         "applies": true,
    310         "answer": false,
    311         "justification": "No hyperparameter search is described. The parameters in Table I (T=15, I=9, etc.) appear chosen without justification or search."
    312       },
    313       "best_config_selection_justified": {
    314         "applies": true,
    315         "answer": false,
    316         "justification": "Table I presents parameter choices (T=15 code responses, I=9 iterations, N instructions per round) without justification for how these values were selected or whether alternatives were tried."
    317       },
    318       "multiple_comparison_correction": {
    319         "applies": false,
    320         "answer": false,
    321         "justification": "No statistical tests are performed, so multiple comparison correction is not applicable."
    322       },
    323       "self_comparison_bias_addressed": {
    324         "applies": true,
    325         "answer": false,
    326         "justification": "The authors evaluate their own system against their own implementation of baselines (SFT variant, base model configuration) without acknowledging potential self-comparison bias. The GPT-3.5 baseline may also be disadvantaged by not receiving ST-specific prompting."
    327       },
    328       "compute_budget_vs_performance": {
    329         "applies": true,
    330         "answer": false,
    331         "justification": "The fine-tuned model requires significant compute (9 DPO iterations × 15 samples per intent × GPT-3.5 expert queries) beyond the baseline GPT-3.5 single-query inference. This compute asymmetry is not discussed or controlled for."
    332       },
    333       "benchmark_construct_validity": {
    334         "applies": true,
    335         "answer": false,
    336         "justification": "The evaluation uses intents from APPS (Python competitive programming) converted to ST and OSCAT (PLC library code). No discussion of whether these converted intents represent realistic industrial PLC programming tasks or whether the benchmark measures actual PLC code generation capability."
    337       },
    338       "scaffold_confound_addressed": {
    339         "applies": false,
    340         "answer": false,
    341         "justification": "No scaffolding is involved. The comparison is between model outputs directly, not between different scaffolded systems."
    342       }
    343     },
    344     "data_leakage": {
    345       "temporal_leakage_addressed": {
    346         "applies": true,
    347         "answer": false,
    348         "justification": "APPS was published in 2021 and OSCAT is publicly available. Phi-3 was trained after these dates. The paper does not discuss whether the model had prior exposure to these datasets or their solutions during pre-training."
    349       },
    350       "feature_leakage_addressed": {
    351         "applies": true,
    352         "answer": false,
    353         "justification": "No discussion of whether the evaluation setup leaks information. The intents used for evaluation may overlap with training signal if the model has seen APPS problems during pre-training."
    354       },
    355       "non_independence_addressed": {
    356         "applies": true,
    357         "answer": false,
    358         "justification": "Training intents (100 OSCAT + 900 APPS) and evaluation intents (100 OSCAT + 100 APPS) are drawn from the same source datasets. Whether they share structural patterns, similar problem formulations, or near-duplicates is not discussed."
    359       },
    360       "leakage_detection_method": {
    361         "applies": true,
    362         "answer": false,
    363         "justification": "No leakage detection or prevention methods are applied. No canary strings, membership inference, n-gram overlap analysis, or temporal splits are used."
    364       }
    365     }
    366   },
    367   "claims": [
    368     {
    369       "claim": "The proposed online DPO method achieves ~70% compilation success rate for ST code, up from 7% baseline.",
    370       "evidence": "Fig. 3A shows compilation rate Pc improving from ~7% (base model) to ~70% after 9 DPO iterations. Single-run point estimates without error bars.",
    371       "supported": "moderate"
    372     },
    373     {
    374       "claim": "Semantic correctness rate peaks at ~45% as measured by GPT-4 evaluation.",
    375       "evidence": "Fig. 3B shows semantic correctness Ps reaching ~45%. Evaluated by GPT-4-1106-preview, not human domain experts. No validation that GPT-4 judgments correlate with actual functional correctness.",
    376       "supported": "weak"
    377     },
    378     {
    379       "claim": "The method outperforms GPT-3.5 Turbo on ST code generation across all three metrics.",
    380       "evidence": "Fig. 3 shows the fine-tuned model exceeding GPT-3.5 Turbo on Pc (~70% vs ~40%), Ps (~45% vs ~25-30%), and Pj (~39% vs ~15-20%).",
    381       "supported": "moderate"
    382     },
    383     {
    384       "claim": "The framework outperforms state-of-the-art models and proves highly suitable for industrial automation applications.",
    385       "evidence": "Only compared against GPT-3.5 Turbo as an external baseline. No comparison against GPT-4, code-specialized models, or evaluation in industrial settings. No real-world deployment.",
    386       "supported": "weak"
    387     },
    388     {
    389       "claim": "Performance improvements are relatively constantly growing over iterations.",
    390       "evidence": "Fig. 3 shows most improvement occurring in iterations 1-2, then plateauing. The claim of 'constantly growing' contradicts the visible plateau in the figures.",
    391       "supported": "weak"
    392     }
    393   ],
    394   "red_flags": [
    395     {
    396       "flag": "LLM-as-judge circular evaluation",
    397       "detail": "GPT-3.5 is used as the semantic expert during DPO training, and GPT-4 (same model family) is used for final evaluation. The paper claims 'cross-validation between different GPT versions' but both share similar biases and training data. No human expert validation of the semantic judgments."
    398     },
    399     {
    400       "flag": "Overclaiming beyond evidence",
    401       "detail": "The abstract claims 'outperforms state-of-the-art models' (plural) based on comparison against only GPT-3.5 Turbo. The conclusion states the approach 'pav[es] the way for total automation of industry' based on 200 evaluation intents with ~39% joint correctness."
    402     },
    403     {
    404       "flag": "Undisclosed conflict of interest",
    405       "detail": "All authors are Siemens Technology Department employees. Siemens manufactures PLCs and would benefit commercially from PLC code generation tools. No conflict of interest or funding statement is included."
    406     },
    407     {
    408       "flag": "No statistical rigor",
    409       "detail": "All results are single-run point estimates with no error bars, no variance reporting, no significance tests, and no seed sensitivity analysis. It is impossible to assess whether the improvements are robust or the result of a lucky initialization."
    410     },
    411     {
    412       "flag": "Missing competitive baselines",
    413       "detail": "GPT-3.5 is the only external baseline despite GPT-4, CodeLlama, DeepSeek-Coder, and other code generation models being available in 2024. GPT-4 is used only as evaluator, not as a generation baseline, creating a suspiciously asymmetric comparison."
    414     },
    415     {
    416       "flag": "Construct validity concern",
    417       "detail": "Evaluation intents are derived from Python competitive programming problems (APPS) converted to ST. This may not represent realistic industrial PLC programming tasks, undermining claims about industrial applicability."
    418     }
    419   ],
    420   "cited_papers": [
    421     {
    422       "title": "Grounded copilot: How programmers interact with code-generating models",
    423       "authors": ["S. Barke", "M. B. James", "N. Polikarpova"],
    424       "year": 2022,
    425       "arxiv_id": "2206.15000",
    426       "relevance": "Empirical study of how developers interact with AI code generation tools, relevant to understanding AI programming productivity."
    427     },
    428     {
    429       "title": "Evaluating large language models trained on code",
    430       "authors": ["M. Chen", "J. Tworek", "H. Jun"],
    431       "year": 2021,
    432       "arxiv_id": "2107.03374",
    433       "relevance": "Foundational paper on Codex/HumanEval establishing LLM code generation evaluation methodology."
    434     },
    435     {
    436       "title": "Training language models to follow instructions with human feedback",
    437       "authors": ["L. Ouyang", "J. Wu", "X. Jiang"],
    438       "year": 2022,
    439       "arxiv_id": "2203.02155",
    440       "relevance": "InstructGPT/RLHF paper establishing the alignment methodology that this work builds upon."
    441     },
    442     {
    443       "title": "Direct preference optimization: Your language model is secretly a reward model",
    444       "authors": ["R. Rafailov", "A. Sharma", "E. Mitchell", "S. Ermon", "C. D. Manning", "C. Finn"],
    445       "year": 2023,
    446       "arxiv_id": "2305.18290",
    447       "relevance": "Core DPO method paper that this work extends to iterative online code generation training."
    448     },
    449     {
    450       "title": "LLM4PLC: Harnessing large language models for verifiable programming of PLCs in industrial control systems",
    451       "authors": ["M. Fakih", "R. Dharmaji", "Y. Moghaddas"],
    452       "year": 2024,
    453       "doi": "10.1145/3639477.3639743",
    454       "relevance": "Prior work on LLM-based PLC code generation with fine-tuning and verification, directly comparable approach."
    455     },
    456     {
    457       "title": "CodeRL: Mastering code generation through pretrained models and deep reinforcement learning",
    458       "authors": ["H. Le", "Y. Wang", "A. D. Gotmare", "S. Savarese", "S. C. H. Hoi"],
    459       "year": 2022,
    460       "arxiv_id": "2207.01780",
    461       "relevance": "RL-based code generation improvement using compiler feedback, a precursor approach to the online DPO method in this paper."
    462     },
    463     {
    464       "title": "StepCoder: Improve code generation with reinforcement learning from compiler feedback",
    465       "authors": ["S. Dou", "Y. Liu", "H. Jia"],
    466       "year": 2024,
    467       "arxiv_id": "2402.01391",
    468       "relevance": "Uses compiler feedback with RL for code generation improvement, closely related methodology."
    469     },
    470     {
    471       "title": "MapCoder: Multi-agent code generation for competitive problem solving",
    472       "authors": ["M. A. Islam", "M. E. Ali", "M. R. Parvez"],
    473       "year": 2024,
    474       "arxiv_id": "2405.11403",
    475       "relevance": "Multi-agent approach to code generation for competitive programming, relevant to LLM code generation evaluation."
    476     },
    477     {
    478       "title": "Code generation with AlphaCodium: From prompt engineering to flow engineering",
    479       "authors": ["T. Ridnik", "D. Kredo", "I. Friedman"],
    480       "year": 2024,
    481       "arxiv_id": "2401.08500",
    482       "relevance": "Iterative code generation approach using test feedback, related to compiler-feedback training paradigm."
    483     },
    484     {
    485       "title": "Measuring coding challenge competence with APPS",
    486       "authors": ["D. Hendrycks", "S. Basart", "S. Kadavath"],
    487       "year": 2021,
    488       "arxiv_id": "2105.09938",
    489       "relevance": "Defines the APPS benchmark used as the primary data source in this paper; important for code generation evaluation."
    490     },
    491     {
    492       "title": "Direct language model alignment from online AI feedback",
    493       "authors": ["S. Guo", "B. Zhang", "T. Liu"],
    494       "year": 2024,
    495       "arxiv_id": "2402.04792",
    496       "relevance": "Introduces the Online AI Feedback (OAIF) method that directly inspires the iterative online DPO approach in this paper."
    497     },
    498     {
    499       "title": "Large language monkeys: Scaling inference compute with repeated sampling",
    500       "authors": ["B. Brown", "J. Juravsky", "R. Ehrlich"],
    501       "year": 2024,
    502       "arxiv_id": "2407.21787",
    503       "relevance": "Shows that generating many code samples improves output quality, motivating the T=15 sampling strategy used in this paper."
    504     }
    505   ]
    506 }

Impressum · Datenschutz