Skip to content

Commit 1e7e4fb

Browse files
JoelNiemeladeboer-tim
JoelNiemela
authored and
deboer-tim
committed
Update broken links and other content errors in various READMEs
1 parent d991e2b commit 1e7e4fb

12 files changed

Lines changed: 31 additions & 31 deletions

File tree

‎BalloonUtility/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The ICPC Balloon Utility
22

3-
![](docs/balloonIcon.png)
3+
<img src="docs/balloonIcon.png" width="50">
44

55
An ICPC Tool
66

@@ -55,11 +55,11 @@ screen will be unpopulated as shown above.)
5555
In order to use the BU once it is started, it must
5656
be connected to the output of a _Contest Control System (CCS)_.
5757
The Balloon Utility will work with any CCS or the CDS which is
58-
compliant with the [Contest API Specification](https://ccs-specs.icpc.io/contest_api).
58+
compliant with the [Contest API Specification](https://ccs-specs.icpc.io/2026-01/contest_api).
5959
Tools known to produce compliant event feeds include
6060
[Contest Data Server](https://tools.icpc.global/cds/),
6161
[DOMjudge](https://www.domjudge.org),
62-
[PC-Squared](http://pc2.ecs.csus.edu/pc2), and
62+
[PC-Squared](https://pc2ccs.github.io/), and
6363
[Kattis](https://www.kattis.com);
6464
other Contest Control Systems may also produce compatible event feeds and
6565
hence work with the Balloon Utility.

‎CDS/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The ICPC Contest Data Server (CDS)
22

3-
![](docs/cdsIcon.png)
3+
<img src="docs/cdsIcon.png" width="50">
44

55
An ICPC Tool
66

@@ -153,7 +153,7 @@ The attributes associated with this element are as follows:
153153
segment of the path (e.g. 'test' in 'C:\\icpc\\test').
154154

155155
* path: specifies the full path to a Contest Package defining the organization of the contest
156-
(config files, logos, etc.). See the [Contest Package](https://ccs-specs.icpc.io/2022-07/contest_package) specification for details on how
156+
(config files, logos, etc.). See the [Contest Package](https://ccs-specs.icpc.io/2026-01/contest_package) specification for details on how
157157
to organize a Contest Package. Note that _the path attribute is required_; the CDS will not
158158
operate if it does not have a folder to store contest related data, even when it is empty and getting all data from the CCS.
159159

‎CoachView/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The ICPC Coach View
22

3-
![](docs/coachViewIcon.png)
3+
<img stc="docs/coachViewIcon.png" width="50">
44

55
An ICPC Tool
66

@@ -10,7 +10,7 @@ The Coach View is a software component designed to provide the ability for spect
1010
(coaches as well as other interested people) to view either or both of a selected team's desktop (machine screen)
1111
or web camera during a contest. It requires that the Contest Administrator configure desktop
1212
and/or webcam streaming from team machines during the contest, and also requires a
13-
[Contest API](https://ccs-specs.icpc.io/contest_api) source that implements video streaming, for
13+
[Contest API](https://ccs-specs.icpc.io/2026-01/contest_api) source that implements video streaming, for
1414
example the ICPC Tools [Contest Data Server](https://tools.icpc.global/cds/).
1515

1616
The Coach View provides the ability for a coach to select a specific team by name or team number and to view

‎ContestUtil/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Contest Utilities
22

3-
![](docs/contestUtilsIcon.png)
3+
<img src="docs/contestUtilsIcon.png" width="50">
44

55
An ICPC Tool
66

‎PresAdmin/README.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The ICPC Presentation Admin
22

3-
![](docs/adminIcon.png){width=50}
3+
<img src="docs/adminIcon.png" width="50">
44

55
An ICPC Tool
66

@@ -20,17 +20,17 @@ Other presentations show data such as the languages being used,
2020
the current number of solutions to each contest problem,
2121
notifications that a particular team has just solved a particular problem,
2222
and so forth, all updating in real time based on input from a
23-
[Contest Control System (CCS)](https://ccs-specs.icpc.io/ccs_system_requirements).
23+
[Contest Control System (CCS)](https://ccs-specs.icpc.io/2026-01/ccs_system_requirements).
2424
There are also pre-defined presentations for showing a variety of user-selected
2525
data such as team photographs, contest logos and related images,
2626
local sites of interest, fireworks for the end
2727
of the contest, and so forth.
2828

2929
The ICPC Presentation System will work with any
3030
CCS that produces an event feed which is
31-
compliant with the [Contest API](https://ccs-specs.icpc.io/contest_api).
31+
compliant with the [Contest API](https://ccs-specs.icpc.io/2026-01/contest_api).
3232
Systems known to produce compliant event feeds include
33-
[PC-Squared](http://pc2.ecs.csus.edu) and
33+
[PC-Squared](https://pc2ccs.github.io/) and
3434
[Kattis](https://www.kattis.com);
3535
other Contest Control Systems may also produce compatible event feeds and
3636
hence work with the Presentation System.

‎PresContest/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,8 @@ When a Presentation Client is started it must be told, in addition to what prese
4242
where to obtain its input data (images, contest events, etc.).
4343
This is referred to as specifying a _contest source_.
4444
Presentation Clients can obtain their input data from two different types of contest sources:
45-
a compliant [_Contest API_](https://ccs-specs.icpc.io/contest_api), or a
46-
a [_Contest Package_](https://ccs-specs.icpc.io/2022-07/contest_package) folder.
45+
a compliant [_Contest API_](https://ccs-specs.icpc.io/2026-01/contest_api), or a
46+
a [_Contest Package_](https://ccs-specs.icpc.io/2026-01/contest_package) folder.
4747

4848
When connecting to a live contest via the Contest API, the Presentation Client works
4949
by reading the _event feed_.
@@ -52,7 +52,7 @@ compliant with the Contest API specification.
5252
Tools known to produce compliant event feeds include
5353
[Contest Data Server](https://tools.icpc.global/cds/),
5454
[DOMjudge](https://www.domjudge.org),
55-
[PC-Squared](http://pc2.ecs.csus.edu/pc2), and
55+
[PC-Squared](https://pc2ccs.github.io/), and
5656
[Kattis](https://www.kattis.com);
5757
other Contest Control Systems may also produce compatible event feeds and
5858
hence work with the Presentation System.

‎ProblemSet/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
# The ICPC Problem Set Editor
22

3-
![](docs/problemSetIcon.png){width=50}
3+
<img src="docs/problemSetIcon.png" width="50">
44

55
An ICPC Tool
66

77
## Introduction
88

99
The ICPC Problem Set Editor is a tool for creating and editing _problemset.yaml_ files,
1010
which define the list of contest problems
11-
and their colors for a [CLICS-compliant](https://ccs-specs.icpc.io/ccs_system_requirements)
11+
and their colors for a [CLICS-compliant](https://ccs-specs.icpc.io/2026-01/ccs_system_requirements)
1212
Contest Control System (CCS).
1313

14-
The following shows a screen shot of the editor in action:
14+
The following shows a screenshot of the editor in action:
1515

1616
![Problem Set editor](docs/ProblemSetScreenShot.png)
1717

‎README.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Welcome to the ICPC Tools!
88
The ICPC Tools are a set of tools to support running programming contests. For the latest downloads, please go to the [ICPC Tools website](https://tools.icpc.global).
99

1010
Each of the ICPC tools can be used individually, or together in any combination. They are all designed to support
11-
the REST-based [Contest API](https://ccs-specs.icpc.io/2021-11/contest_api) as defined by the Competitive Learning Initiative (CLI).
11+
the REST-based [Contest API](https://ccs-specs.icpc.io/2026-01/contest_api) as defined by the Competitive Learning Initiative (CLI).
1212
Some features require extensions to the specification, and those are described [here](doc/spec-extensions.md).
1313

1414
These tools were built to support the
@@ -30,7 +30,7 @@ Contest Utilities | A variety of useful contest-related utilities: event feed va
3030

3131
## Contest Control System Compatibility
3232

33-
The ICPC Tools are built to work with any Contest Control System (CCS) that supports the REST-based [Contest API](https://ccs-specs.icpc.io/2021-11/contest_api).
33+
The ICPC Tools are built to work with any Contest Control System (CCS) that supports the REST-based [Contest API](https://ccs-specs.icpc.io/2026-01/contest_api).
3434

3535
To be more specific, the only part of the Contest API that is strictly required is the event feed and any file
3636
references that the feed refers to. If your CCS correctly supports the event feed, then all of the ICPC Tools will
@@ -87,10 +87,10 @@ A [Docker image](https://ghcr.io/icpctools/cds) is provided to run the CDS witho
8787
The basic way to run it, is to run
8888

8989
```bash
90-
docker run --name cds --rm -it -p 8080:8080 -p 8443:8443 -e CCS_URL=https://www.domjudge.org/demoweb/api/contests/nwerc18 -e CCS_USER=admin -e CCS_PASSWORD=admin ghcr.io/icpctools/cds:2.2.407
90+
docker run --name cds --rm -it -p 8080:8080 -p 8443:8443 -e CCS_URL=https://www.domjudge.org/demoweb/api/contests/nwerc18 -e CCS_USER=admin -e CCS_PASSWORD=admin ghcr.io/icpctools/cds:2.7.1359
9191
```
9292

93-
Replace `https://www.domjudge.org/demoweb/api/contests/nwerc18` with your CCS contest API URL, `CCS_USER` with a user with admin privileges to the CCS URL, `CCS_PASSWORD` with the password for the given user and `2.2.407` with the version of the CDS you want to run.
93+
Replace `https://www.domjudge.org/demoweb/api/contests/nwerc18` with your CCS contest API URL, `CCS_USER` with a user with admin privileges to the CCS URL, `CCS_PASSWORD` with the password for the given user and `2.7.1359` with the version of the CDS you want to run.
9494

9595
Now you can access the CDS at https://localhost:8443/.
9696

‎Resolver/README.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# The ICPC Resolver
22

3-
![](docs/resolverIcon.png)
3+
<img src="docs/resolverIcon.png" width="50">
44

55
An ICPC Tool
66

@@ -98,11 +98,11 @@ credentials are only given to trusted contest staff or not distributed until the
9898
### Input Data Sources
9999

100100
The Resolver works with any CCS or the CDS that produces an event feed which is
101-
compliant with the [Contest API Specification](https://ccs-specs.icpc.io/contest_api).
101+
compliant with the [Contest API Specification](https://ccs-specs.icpc.io/2026-01/contest_api).
102102
Tools known to produce compliant event feeds include
103103
[Contest Data Server](https://tools.icpc.global/cds/),
104104
[DOMjudge](https://www.domjudge.org),
105-
[PC-Squared](http://pc2.ecs.csus.edu/pc2), and
105+
[PC-Squared](https://pc2ccs.github.io/), and
106106
[Kattis](https://www.kattis.com);
107107
other Contest Control Systems may also produce compatible event feeds and
108108
hence work with the Resolver.
@@ -112,7 +112,7 @@ three different sources: a _Contest Package_ folder, a _Contest API_ source, or
112112

113113
If the Resolver is started with the first argument being a path (relative or absolute)
114114
to a folder, it will expect the folder to contain contest data as per the
115-
[Contest Package](https://ccs-specs.icpc.io/2022-07/contest_package) specification.
115+
[Contest Package](https://ccs-specs.icpc.io/2026-01/contest_package) specification.
116116
If the Resolver is started with the first argument pointing to a file, it will expect
117117
the file to be an event feed JSON file.
118118

@@ -421,7 +421,7 @@ The specification of what groups exist in a contest comes from the event feed
421421
The CCS used in the World Finals is configured to define six "regions" (groups):
422422
North America, Latin American (comprising Central and South America),
423423
Europe, Asia, Africa and the Middle East, and the South Pacific.
424-
(See the interactive [ICPC Regional Finder map](https://icpc.baylor.edu/regionals/finder) for definitions of the
424+
(See the interactive [ICPC Regional Finder map](https://icpc.global/regionals/finder) for definitions of the
425425
precise boundaries of ICPC Regions.)
426426
The highest placing team at the World Finals from each of the six ICPC regions
427427
receives an award acknowledging their accomplishment as "Regional Champion".

‎website/content/coach-view.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The Coach View is a software component designed to provide the ability for spect
1111
(coaches as well as other interested people) to view either or both of a selected team's desktop (machine screen)
1212
or web camera during a contest. It requires that the Contest Administrator configure desktop
1313
and/or webcam streaming from team machines during the contest, and also requires a
14-
[Contest API](https://ccs-specs.icpc.io/contest_api) source that implements video streaming, for
14+
[Contest API](https://ccs-specs.icpc.io/2026-01/contest_api) source that implements video streaming, for
1515
example the ICPC Tools [Contest Data Server](/cds).
1616

1717
The Coach View provides the ability for a coach to select a specific team by name or team number and to view

0 commit comments

Comments
 (0)