-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
2 changed files
with
57 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# Title | ||
## Venue | ||
- which conference or journal is targeted | ||
- explain reason (impact factor, audience, related work was published there) | ||
|
||
## Authors | ||
(student leading, other students and collaborators, then primary supervisor) | ||
|
||
## Motivation of problem to be solved | ||
An image or two and a couple of bullets, cite review / paper stating the RQ/field, formulate as abstract. | ||
- what is the problem ? (cite review) | ||
- why do we (or collaborators) care ? (cite) | ||
- what do we have now | ||
- what do we want (why isn't what we have good enough?) | ||
- how do/did we get it | ||
|
||
### Computing Science Task | ||
- [ ] Discovery | ||
- [ ] Classification | ||
- [ ] Regression | ||
- [ ] Automation | ||
- [ ] Clustering | ||
- [ ] Acceleration | ||
|
||
## Related work | ||
~ 5 references | ||
### Title | ||
- [ ] URL | ||
- [ ] Group, Year | ||
- [ ] Venue | ||
- [ ] weakness / area to improve | ||
|
||
## Contribution claims | ||
(bulleted list of concise items, the section ending the introduction: in this work we ... | ||
|
||
## Method | ||
(outline the main novel equation/algorithm/idea) | ||
|
||
### Method choice justification | ||
(why this method and not another, why these steps) | ||
|
||
## Anticipated results | ||
that back up the contribution claims and outperform competing methods (which state of the art competing methods are you comparing with? Are you sure there are no newer/better methods to compare with? How are you ensuring it is a fair comparison (e.g. using same training and test data, e.g. using public challenge data)? How are you sure that you are faithful to the compering methods (e.g. did you use code from the authors of competing methods)? how will the results be presented, show mock-up graphs, tables with proper headings and labels) | ||
## Data | ||
- which data set | ||
- url | ||
- license ? | ||
- disclosure (ethics approval / public private) | ||
- pre/post processing / annotation needed ? | ||
|
||
## Repository | ||
- URL (gitlab/github) containing code / paper resources | ||
|
||
## Timeline | ||
### Deadline abstract | ||
### Deadline full submission | ||
### Plan with milestones |
Empty file.