Documentation
¶
Overview ¶
Package problem is a package for test problem manipulation.
Overview ¶
A test problem is store in a directory, for example, "dir", with following structure:
|-dir/problem.json |-dir/data/ |---dir/tests/ |---dir/subtasks/ |---dir/static/ |-dir/workflow/ stores test workflow |---dir/workflow/graph.json stores the workflow graph |-dir/statement/ stores statement files |---dir/statement/s.[lang][id].md stores statement files |---dir/statement/t.[lang][id].md stores tutorial files |---dir/statement/xxx stores assert files |-dir/patch/ stores added files
Tests ¶
Usually a problem contains multiple testcases, whose data are stored in dir/data/tests/, since a contestant's submission should be tested enoughly before being considered correct. All testcases have the same fields.
Testcase may have "_score" field, whose value is either a number string or "average".
Subtask ¶
To better assign points to testcases with different intensity, it's common to set up several subtasks for the problem, each containing a series of testcases.
Note that if subtask is enabled, independent testcases (i.e. not in a subtask) are not allowed.
If subtask data occured (at least one field, at least one record), subtask is enabled.
For some problem, different subtasks use different files to test contestant' submission, for example, checker or input generator. Thus these data are stored in dir/data/tests/. Again, all subtasks' data have the same fields.
Subtask may have "_score" field, whose value is a number string.
For problem enabling subtask, its testcase and subtask both contain "_subtaskid" field, determining which subtask the testcase belongs to.
Static Data ¶
Common data are stored in dir/data/static/ shared by all testcases.
Testcase Score ¶
Score of a testcase is calculated as follows:
If subtask is enabled, testcase's "_score" is ignored, its score is {subtask score} / {number of tests in this subtask}.
Otherwise, if "average" is specified for "_score" field, its score is {problem total score} / {number of testcases}. Else its "_score" should be a number string, denoting its score.
Statement ¶
Markdown is the standard format of statement. Other formats may be supported in the future.
Workflow ¶
See github.com/sshwy/yaoj-core/workflow.
Problem gives workflow 4 datagroups naming "testcase", "subtask", "static" and "submission" respectively.
Index ¶
- Variables
- func GuessLang(lang string) string
- type CalcMethod
- type DataInfo
- type ProbData
- func (r *ProbData) AddFile(name string, pathname string) (string, error)
- func (r *ProbData) AddFileReader(name string, file io.Reader) (string, error)
- func (r *ProbData) Dir() string
- func (r *ProbData) Export(dir string) error
- func (r *ProbData) Finalize() error
- func (r *ProbData) IsSubtask() bool
- func (r *ProbData) SetStmt(lang string, file string)
- func (r *ProbData) SetValFile(rcd record, field string, filename string) error
- func (r *ProbData) SetWkflGraph(serial []byte) error
- func (r *ProbData) Workflow() workflow.Workflow
- type Problem
- type Result
- type SubmConf
- type SubmLimit
- type Submission
- type SubtResult
- type SubtaskInfo
- type TestInfo
Constants ¶
This section is empty.
Variables ¶
Functions ¶
Types ¶
type CalcMethod ¶ added in v0.0.16
type CalcMethod int
子任务中测试点得分的汇总方式
const ( // default Mmin CalcMethod = iota Mmax Msum )
type DataInfo ¶ added in v0.0.16
type DataInfo struct {
IsSubtask bool
Fullscore float64
CalcMethod CalcMethod //计分方式
Subtasks []SubtaskInfo
// 静态文件
Static map[string]string //other properties of data
}
type ProbData ¶ added in v0.0.7
type ProbData struct {
// Usually 100.
// Full score can be used to determine the point of testcase
Fullscore float64
CalcMethod CalcMethod
// "tests" _subtaskid, _score ("average", {number})
Tests table
// "subtask" _subtaskid, _score, _depend (separated by ",")
Subtasks table
// "submission" configuration
Submission map[string]SubmLimit
// "static"
Static record
// "statement"
// Statement has 1 record. "s.{lang}", "t.{lang}" represents statement and
// tutorial respectively. "_tl" "_ml" "_ol" denotes cpu time limit (ms),
// real memory limit (MB) and output limit (MB) respectively.
// Others are just filename.
Statement record
// contains filtered or unexported fields
}
Problem data module
func LoadProbData ¶ added in v0.0.7
load problem from a dir
func NewProbData ¶ added in v0.0.7
create a new problem in an empty dir
func (*ProbData) AddFileReader ¶ added in v0.0.8
func (*ProbData) Export ¶ added in v0.0.7
export the problem's data to another empty dir and change itself to the new one
func (*ProbData) SetValFile ¶ added in v0.0.8
func (*ProbData) SetWkflGraph ¶ added in v0.0.7
Set workflow graph
type Problem ¶
type Problem interface {
// 将题目打包为一个文件（压缩包）
DumpFile(filename string) error
// 获取题面，lang 见 http://www.lingoes.net/zh/translator/langcode.htm
Stmt(lang string) []byte
// 题解
Tutr(lang string) []byte
// 附加文件
Assert(filename string) (*os.File, error)
// 获取提交格式的数据表格
SubmConf() SubmConf
// 评测用的
Data() *ProbData
// 展示数据
DataInfo() DataInfo
}
type Result ¶
type Result struct {
IsSubtask bool
CalcMethod CalcMethod
Subtask []SubtResult
}
Problem result
type SubmLimit ¶ added in v0.0.9
type SubmLimit struct {
// 接受的语言，nil 表示所有语言
Langs []utils.LangTag
// 接受哪些类型的文件，必须设置值
Accepted utils.CtntType
// 文件大小，单位 byte
Length uint32
}
limitation for any file submitted
type Submission ¶ added in v0.0.11
存储文件的路径
type SubtResult ¶
Subtask result
Source Files