Debian Codegraph @

submodules/subprojects/highs/.coin-or/projDesc.xml

raw
1 <?xml version="1.0" encoding="UTF-8"?>
2 <?xml-stylesheet type = "text/xsl" href = "https://projects.coin-or.org/svn/CoinWeb/trunk/projects/autoGen.xsl"?>
3 <projectData xmlns="coin-or.org"
4 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
5 xsi:schemaLocation="https://projects.coin-or.org/svn/CoinWeb/trunk/projects/autoGen.xsd">
6
7 <!--
8 This file is a template that you fill in to provide specific information
9 about your project. For project Foo, it is used to generate the page
10 http://www.coin-or.org/projects/Foo.xml
11 Once the template is filled in and checked into your project's repository
12 in the conf/ directory, it will be automatically parsed and displayed
13 in a standard HTML format using XSLT. When users follow the link to
14 your project from the Projects page on the COIN Web site, the generated
15 HTML is what they will see. As an example, have a look at
16 http://www.coin-or.org/projects/Cbc.xml
17 to see the result.
18
19 The file is extensively commented to help you understand where to fill
20 in the various pieces of required information.
21
22 With a few exceptions, elements are *NOT* optional. They must appear in
23 this file, in order, or the file will not pass validation against the
24 schema. Don't delete elements, and don't rearrange them. The schema is
25 in the CoinWeb repo,
26 https://projects.coin-or.org/svn/CoinWeb/trunk/projects/autoGen.xsd
27 for those of you who know and love XML.
28
29 Elements that are optional in the generated HTML will be omitted
30 if you leave them empty (i.e., nothing but whitespace). The XSL
31 that transforms this file into HTML is also in the CoinWeb repo,
32 https://projects.coin-or.org/svn/CoinWeb/trunk/projects/autoGen.xsl
33
34 If you want to display non-ascii characters, you must use numeric
35 character references, e.g., &#xe8; or &#232, but *NOT* &egrave;. The
36 named entities are not necessarily available when the XML is processed.
37
38 *DO NOT* use HTML markup in blocks of text. It screws up the validation.
39
40 XML comments are block comments, delimited by the character sequences
41 you see at the start and end of this comment block. Comments don't nest.
42 -->
43
44 <projectBasics>
45
46 <!-- Fill in your project's name in this block. -->
47 <!-- For example, for Creme you could write: -->
48 <!-- -->
49 <!-- <projectName>Cr&#xe8;me</projectName> -->
50 <!-- -->
51 <!-- This string is displayed in the banner at the top of the -->
52 <!-- project page. If you do not define projectRepo (next -->
53 <!-- block) the same string will be used to construct the URL -->
54 <!-- of your project's Trac page. So if projectName isn't -->
55 <!-- plain ascii, be sure to define projectRepo. -->
56 <!-- Fill in your text below (outside this comment block). -->
57
58 <projectName>HiGHS</projectName>
59
60 <!-- Fill in with the appropriate string to construct a URL -->
61 <!-- for your project's Trac page and SVN repository. For -->
62 <!-- Creme, the correct string is -->
63 <!-- -->
64 <!-- <projectRepo>Creme</projectName> -->
65 <!-- -->
66 <!-- Use the right value for the URL for your project. -->
67 <!-- Fill in your text below (outside this comment block). -->
68
69 <projectRepo>HiGHS</projectRepo>
70
71 <!-- Fill in a brief description of your project here. -->
72 <!-- For example, for SYMPHONY, you might put: -->
73 <!-- -->
74 <!-- <projectDescription> -->
75 <!-- SYMPHONY is an open-source generic MILP solver, -->
76 <!-- callable library, and extensible framework for -->
77 <!-- implementing customized solvers for mixed-integer -->
78 <!-- linear programs (MILPs). Blah, blah, blah. -->
79 <!-- </projectDescription> -->
80 <!-- -->
81 <!-- Fill in your text below (outside this comment block) -->
82
83 <projectDescription>HiGHS is a high performance serial and parallel solver for large scale sparse linear programming problems. Written in C++, and with no dependence on other COIN-OR software or third party code, it has interfaces to a range of other popular languages (C, C#, FORTRAN, Julia and Python, to date) and examples of their use. Problems are solved using the dual simplex method. Further solution techniques (primal simplex and interior point), extension to quadratic programming and proper documentation are being developed actively. Although HiGHS is freely available under the MIT license, we would be pleased to learn about users' experience and give advice and support via email sent to [email protected].
84 </projectDescription>
85
86 <!-- Provide a one or two sentence description of your -->
87 <!-- project. This description will be used in the listings on -->
88 <!-- the main COIN-OR projects page. For DyLP, for example, -->
89 <!-- <projectShortDescription> -->
90 <!-- An implementation of the dynamic simplex method. -->
91 <!-- </projectShortDescription> -->
92 <!-- -->
93 <!-- Fill in your text below (outside this comment block) -->
94
95 <projectShortDescription>High performance linear optimization software in C++, with interfaces to C, C#, FORTRAN, Julia and Python.
96 </projectShortDescription>
97
98 <!-- Fill in the project manager's name and (obfuscated) -->
99 <!-- e-mail address here. For example, for the SYMPHONY -->
100 <!-- project, you could write -->
101 <!-- -->
102 <!--<projectManager> -->
103 <!-- Ted Ralphs, tkralphs at lehigh dot edu -->
104 <!--</projectManager> -->
105 <!-- -->
106 <!-- Fill in your text below (outside this comment block). -->
107
108 <projectManager>Julian Hall, [email protected]</projectManager>
109
110 <!-- Fill in the URL you would like use for your project's -->
111 <!-- main home page. This could be your Trac page, or a static -->
112 <!-- page (if you have one). For example, for SYMPHONY, the -->
113 <!-- Trac page is -->
114 <!-- -->
115 <!--<projectHomePage> -->
116 <!-- https://projects.coin-or.org/SYMPHONY -->
117 <!--</projectHomePage> -->
118 <!-- -->
119 <!-- Fill in your text below (outside this comment block). -->
120
121 <projectHomePage>http://www.highs.dev/</projectHomePage>
122
123 <!-- Fill in the name of the license your project uses and a -->
124 <!-- link to its page on www.opensource.org. For example, if -->
125 <!-- you use the EPL, you would put -->
126 <!-- -->
127 <!--<projectLicense> -->
128 <!-- Eclipse Public License 1.0 -->
129 <!--</projectLicense> -->
130 <!--<projectLicenseURL> -->
131 <!-- http://www.opensource.org/licenses/eclipse-1.0 -->
132 <!--</projectLicenseURL> -->
133 <!-- -->
134 <!-- Fill in your text below (outside this comment block). -->
135
136 <projectLicense>MIT License</projectLicense>
137 <projectLicenseURL>https://opensource.org/licenses/MIT</projectLicenseURL>
138
139 <!-- Below, you can list other COIN projects your project -->
140 <!-- depends on. These are listed one by one, as in the -->
141 <!-- following example -->
142 <!-- -->
143 <!--<coinLinkedProjects> -->
144 <!-- -->
145 <!-- <coinProject> -->
146 <!-- <repoName>CoinUtils</repoName> -->
147 <!-- </coinProject> -->
148 <!-- -->
149 <!-- <coinProject> -->
150 <!-- <repoName>Ots</repoName> -->
151 <!-- <projectName>OTS</projectName> -->
152 <!-- <projectUrl> -->
153 <!-- http://www.coin-or.org/Ots/index.html -->
154 <!-- </projectUrl> -->
155 <!-- </coinProject> -->
156 <!-- -->
157 <!--</coinLinkedProjects> -->
158 <!-- -->
159 <!-- The <repoName> element of <coinProject> is mandatory. If -->
160 <!-- you do not provide <projectName>, it is assumed to be the -->
161 <!-- same as repoName. If you do not provide <projectUrl>, it -->
162 <!-- is assumed to be http://www.coin-or.org/projects/Foo.xml -->
163 <!-- with `Foo' replaced by the value of <repoName>. -->
164 <!-- Add as many <coinProject> elements as you need below. -->
165
166 <coinLinkedProjects><coinProject><repoName>Osi</repoName></coinProject>
167 </coinLinkedProjects>
168
169 <!-- Below, you can list other packages your project requires -->
170 <!-- or can use as an option. These are listed one-by-one, as -->
171 <!-- in the following example: -->
172 <!-- -->
173 <!--<otherLinkedPackages> -->
174 <!-- -->
175 <!-- <otherPackage> -->
176 <!-- <packageName> -->
177 <!-- GLPK -->
178 <!-- </packageName> -->
179 <!-- <packageURL> -->
180 <!-- http://www.gnu.org/software/glpk/ -->
181 <!-- </packageURL> -->
182 <!-- <requiredOrOptional> -->
183 <!-- Optional -->
184 <!-- </requiredOrOptional> -->
185 <!-- </otherPackage> -->
186 <!-- -->
187 <!-- <otherPackage> -->
188 <!-- <packageName> -->
189 <!-- GNU Readline -->
190 <!-- </packageName> -->
191 <!-- <packageURL> -->
192 <!-- </packageURL> -->
193 <!-- <requiredOrOptional> -->
194 <!-- Optional -->
195 <!-- </requiredOrOptional> -->
196 <!-- </otherPackage> -->
197 <!-- -->
198 <!--</otherLinkedPackages> -->
199 <!-- -->
200 <!-- For each <otherPackage> element, all of <packageName>, -->
201 <!-- <packageURL>, and <requiredOrOptional> must be present, -->
202 <!-- but they can be empty (as shown in the example). Add as -->
203 <!-- many <otherPackage> elements as you need. -->
204
205 <otherLinkedPackages>
206 </otherLinkedPackages>
207
208 <!-- Fill in the programming language(s) used in the project. -->
209 <!-- For example: -->
210 <!--<projectLanguage>C, C++</projectLanguage> -->
211 <!-- -->
212 <!-- Fill in your text below (outside this comment block). -->
213
214 <projectLanguage>C++</projectLanguage>
215
216 <!-- The following fields describe the development status -->
217 <!-- of the project. -->
218
219 <developmentStatus>
220
221 <!-- If you are actively managing your project, use -->
222 <!-- `Active'. Otherwise, change as appropriate. -->
223 <!-- Eventually there may be formal categories. -->
224
225 <activityStatus>Active</activityStatus>
226
227 <!-- The maturity level is determined during project -->
228 <!-- review and should have been reported to you. If not, -->
229 <!-- ask the person who handled your project submission. -->
230 <!-- If all else fails, see -->
231 <!-- http://www.coin-or.org/faqs.html#q18 -->
232 <!-- and make an informed guess. For example, -->
233 <!-- -->
234 <!--<maturityLevel>4</maturityLevel> -->
235 <!-- -->
236
237 <maturityLevel>2</maturityLevel>
238
239 <!-- Having trouble with the automated system that -->
240 <!-- generates stable and release version numbers? If -->
241 <!-- so, you can override one or both with these -->
242 <!-- elements. DO NOT USE unless necessary, as it will -->
243 <!-- your responsibility to keep them up-to-date. Your -->
244 <!-- text will be used verbatim. These two elements -->
245 <!-- are the exception to the rule that elements must -->
246 <!-- appear. These must *NOT* be uncommented unless -->
247 <!-- needed. -->
248
249 <!--
250 <stableVersionNumber></stableVersionNumber>
251 <releaseNumber></releaseNumber>
252 -->
253
254 </developmentStatus>
255
256 <!-- Below, you can list the platforms on which your project -->
257 <!-- has been tested. Again, these are listed one-by-one. -->
258 <!-- Within a <platform>, <operatingSystem> is mandatory and -->
259 <!-- <compiler> is optional. -->
260 <!-- -->
261 <!--<testedPlatforms> -->
262 <!-- -->
263 <!-- <platform> -->
264 <!-- <operatingSystem>Microsoft Windows</operatingSystem> -->
265 <!-- <compiler>MSVC++/cl</compiler> -->
266 <!-- </platform> -->
267 <!-- -->
268 <!-- <platform> -->
269 <!-- <operatingSystem>Microsoft Windows</operatingSystem> -->
270 <!-- <compiler>CYGWIN/cl</compiler> -->
271 <!-- </platform> -->
272 <!-- -->
273 <!--</testedPlatforms> -->
274 <!-- -->
275 <!-- Fill in your text below. Add as many platform elements as -->
276 <!-- you need. -->
277
278 <testedPlatforms>
279 <platform>
280 <operatingSystem>Linux</operatingSystem>
281 <compiler>GCC</compiler>
282 </platform>
283 <platform>
284 <operatingSystem>Linux</operatingSystem>
285 <compiler>CLANG</compiler>
286 </platform>
287 <platform>
288 <operatingSystem>Macos</operatingSystem>
289 <compiler>CLANG</compiler>
290 </platform>
291 <platform>
292 <operatingSystem>Windows</operatingSystem>
293 <compiler>MSVC++</compiler>
294 </platform>
295 </testedPlatforms>
296
297 <!-- The projectCategories element contains a list of category -->
298 <!-- elements. The text of the category elements will be -->
299 <!-- displayed as a comma-separated list and used to classify -->
300 <!-- your project on the main Projects page. The list given -->
301 <!-- here contains standard categories. Please don't create a -->
302 <!-- new one without good reason. Use as many as are -->
303 <!-- appropriate. -->
304
305 <projectCategories>
306
307 <!--"Un-comment" any categories that apply to your project. -->
308
309 <!-- <category> -->
310 <!-- Development tools -->
311 <!-- </category> -->
312 <!-- <category> -->
313 <!-- Graphs -->
314 <!-- </category> -->
315 <!-- <category> -->
316 <!-- Interfaces -->
317 <!-- </category> -->
318 <!-- <category> -->
319 <!-- Metaheuristics -->
320 <!-- </category> -->
321 <!-- <category> -->
322 <!-- Modeling systems -->
323 <!-- </category> -->
324 <!-- <category> -->
325 <!-- Optimization convex non-differentiable -->
326 <!-- </category> -->
327 <category>
328 Optimization deterministic linear continuous
329 </category>
330 <!-- <category> -->
331 <!-- Optimization deterministic linear discrete -->
332 <!-- </category> -->
333 <!-- <category> -->
334 <!-- Optimization deterministic nonlinear -->
335 <!-- </category> -->
336 <!-- <category> -->
337 <!-- Optimization deterministic nonlinear discrete -->
338 <!-- </category> -->
339 <!-- <category> -->
340 <!-- Optimization deterministic semidefinite continuous -->
341 <!-- </category> -->
342 <!-- <category> -->
343 <!-- Optimization stochastic -->
344 <!-- </category> -->
345 <!-- <category> -->
346 <!-- Optimization utility -->
347 <!-- </category> -->
348
349 </projectCategories>
350
351 </projectBasics>
352
353 <!-- Below, you can specify extra links for the left-hand side menu. -->
354 <!-- If you leave an element empty, there will be no corresponding -->
355 <!-- menu item. The first three left-hand links (COIN-OR Home, -->
356 <!-- Projects, Project Management Page) are automatic; you cannot -->
357 <!-- affect them from here. -->
358 <!-- -->
359 <!-- For SYMPHONY, this block would look like this: -->
360 <!-- -->
361 <!-- <leftMenuLinks> -->
362 <!-- -->
363 <!-- <documentation> -->
364 <!-- http://www.coin-or.org/SYMPHONY/man-5.1 -->
365 <!-- </documentation> -->
366 <!-- -->
367 <!-- <sourceCodeDownload> -->
368 <!-- http://www.coin-or.org/download/source/SYMPHONY -->
369 <!-- </sourceCodeDownload> -->
370 <!-- -->
371 <!-- <binaryDownload> -->
372 <!-- http://www.coin-or.org/download/binary/SYMPHONY -->
373 <!-- </binaryDownload> -->
374 <!-- -->
375 <!-- <mailingList> -->
376 <!-- http://list.coin-or.org/mailman/listinfo/coin-symphony -->
377 <!-- </mailingList> -->
378 <!-- </leftMenuLinks> -->
379 <!-- -->
380 <!-- All elements are mandatory! Just leave them empty if you have -->
381 <!-- nothing relevant; the corresponding menu item will not appear. -->
382 <!-- Fill in your text below (outside this comment block). -->
383
384 <leftMenuLinks>
385
386 <documentation> </documentation>
387
388 <sourceCodeDownload>http://github.com/ERGO-Code/HiGHS</sourceCodeDownload>
389
390 <binaryDownload> </binaryDownload>
391
392 <mailingList> </mailingList>
393
394 </leftMenuLinks>
395
396 </projectData>