Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
beat.web
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
beat
beat.web
Merge requests
!169
[doc/user] Improved overview script after recording
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
[doc/user] Improved overview script after recording
userdoc
into
master
Overview
0
Commits
1
Pipelines
0
Changes
1
Merged
André Anjos
requested to merge
userdoc
into
master
9 years ago
Overview
0
Commits
1
Pipelines
0
Changes
1
Expand
0
0
Merge request reports
Viewing commit
92783a9e
Show latest version
1 file
+
11
−
10
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
92783a9e
[doc/user] Improved overview script after recording
· 92783a9e
André Anjos
authored
9 years ago
doc/user/overview/script.rst
+
11
−
10
Options
@@ -266,13 +266,14 @@ Script
your paper.
34. **Say**: You can work with the BEAT platform in many ways. For example, you
can create searches and leaderboards t
hat express your interest. You can
also re-run experiments easily and change
parameters so to test for new
settings.
can create searches and leaderboards t
o track the development of problems
you're interested on. You can
also re-run experiments easily and change
parameters so to test for new
settings.
35. **Say**: For example, let's re-run the experiment with 77 components and
check if, with 50 components how it would work. Let's click on the
experiment link here on the report and go to the experiment page.
check if, with 50 components, the system presents any performance
improvements. Let's click on the experiment link here on the report and go
to the experiment page.
* Action: Go back on the browser
* Outcome: The user report page is shown
@@ -283,7 +284,7 @@ Script
36. **Say**: To re-run an experiment, just click on the "Fork" button located
on the top-right action bar. When you do that, the platform copies the
whole experiment configuration to your work area.
Of course
that experiment
whole experiment configuration to your work area.
The new
that experiment
will be private to you.
* Action: Click on the "fork" action button
@@ -322,8 +323,8 @@ Script
* Outcome: The table is re-ordered
* Action: Show the relative position of the new experiment
40. **Say**: You can change more
more
than the parameters of a experiment. You
can
actually change all aspects of it: the toolchain, the datasets and the
40. **Say**: You can change more than the parameters of a experiment. You
can
actually change all aspects of it: the toolchain, the datasets and the
actual algorithms used to crunch the data. It is all up to you. You can
inspect these components by looking at the different tabs available through
the pop-down button on the top
@@ -338,8 +339,8 @@ Script
42. **Say**: In case you have questions, suggestions or found bugs, please
don't hesitate in posting a message to our development mailing list at
google groups, called "beat-devel". Thanks for your interest
. Keep posted
for new features and bug fixes.
google groups, called "beat-devel". Thanks for your interest
and keep
posted
for new features and bug fixes.
44. Screen shows credits:
Loading