DouDou commited on
Commit
22921de
·
verified ·
1 Parent(s): f2670ef

Upload data3/is_sci_prompt.txt with huggingface_hub

Browse files
Files changed (1) hide show
  1. data3/is_sci_prompt.txt +22 -0
data3/is_sci_prompt.txt ADDED
@@ -0,0 +1,22 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ You will receive the full contents of a code file.
2
+
3
+ Your task is to decide whether this code is related to scientific computing.
4
+
5
+ Decision criteria:
6
+ 1. Only if the code explicitly contains terms clearly related to natural sciences should it be considered scientific computing, for example:
7
+ - Chemistry-related terms: molar mass, stoichiometry, enthalpy, entropy, Gibbs free energy, pH, titration, reaction rate, bond length, molecule, atom, orbital, spectroscopy, chromatography, equilibrium constant, reaction kinetics, electrochemistry, etc.
8
+ - Physics-related terms: velocity, acceleration, force, momentum, energy (in a clearly physical context), potential, kinetic, wave, frequency, wavelength, quantum, spin, Hamiltonian, Schrödinger, thermodynamics, statistical mechanics, electromagnetism, fluid dynamics, optics, etc.
9
+ - Other clear scientific computing terms: simulation, finite element, molecular dynamics, DFT (density functional theory), Monte Carlo, N-body simulation, PDE (partial differential equation), ODE solver, etc.
10
+ 2. These terms must appear in a clear scientific or mathematical context in the code (including comments, variable names, function names), not just as generic words or in unrelated meanings.
11
+ 3. If the code is only general business logic, web development, database operations, machine learning on generic data, string processing, UI, logging, configuration, etc., and does not contain explicit natural science terminology as above, then it is NOT scientific computing related.
12
+ 4. If only generic or ambiguous words appear (e.g., data, analysis, score, model, temperature, pressure, signal) without clear scientific formulas, laws, or discipline-specific context, do NOT treat it as scientific computing.
13
+ 5. Only consider what appears in the code itself. Do NOT infer or guess based on libraries, file names, frameworks, or your external knowledge of typical uses. If there are no explicit natural science terms or concepts, treat it as NOT scientific computing related.
14
+
15
+ Output requirements:
16
+ - If the code IS scientific computing related, output exactly: true
17
+ - If the code is NOT scientific computing related, output exactly: false
18
+ - Do NOT output anything else: no explanations, no spaces, no quotes, no punctuation.
19
+
20
+ Now analyze the following code file content:
21
+
22
+ {CODE_FILE}