This repository has been archived by the owner on Jul 22, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
177 lines (156 loc) · 10.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0"/>
<title>CASICS: Comprehensive and Automated Software Inventory Creation System</title>
<!-- CSS -->
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
<link href="css/materialize.css" type="text/css" rel="stylesheet" media="screen,projection"/>
<link href="css/style.css" type="text/css" rel="stylesheet" media="screen,projection"/>
</head>
<body>
<!-- <nav class="grey lighten-1" role="navigation">
<div class="nav-wrapper container">
<ul class="right hide-on-med-and-down">
<li><a href="#">Navbar Link</a></li>
</ul>
<ul id="nav-mobile" class="side-nav">
<li><a href="#">Navbar Link</a></li>
</ul>
<a href="#" data-activates="nav-mobile" class="button-collapse"><i class="material-icons">menu</i></a>
</div>
</nav>
-->
<div class="section no-pad-bot" id="index-banner">
<div class="container">
<h1 class="header center deep-teal-text"><img width="70px" style="padding-right: 15px" src="graphics/casics-logo-in-steel-teal.svg" onerror="this.src='graphics/casics-logo-in-steel-teal.png'" />CASICS</h1>
<div class="row center">
<h5 class="header col s12 light">Comprehensive and Automated Software Inventory Creation System</h5>
<p class="light">A wealth of software is available, and more is being created. Yet, <em>finding</em> software for a given purpose remains difficult. Few resources exist to help users discover alternatives or understand the differences between them.</p>
</div>
<div class="row">
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">explore</i></h3>
<h5 class="center light">Why not just search in Google?</h5>
<p class="light">(1) It's often difficult to think of good search terms.
(2) Good software can be buried in thousands of search results.
(3) Search results don't tell you <em>differences</em> between software features.</p>
</div>
</div>
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">chat_bubble_outline</i></h3>
<h5 class="center light">Why not just ask your colleagues?</h5>
<p class="light">(1) Most people don't know about all the possible options or how the options differ. (2) Answers are potentially biased: what people <em>do</em> know may be out of date or be incorrect.</p>
</div>
</div>
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">description</i></h3>
<h5 class="center light">Why not look in the literature?</h5>
<p class="light">(1) Papers are static, but software evolves rapidly.
(2) Not all software projects have a publication associated with them.
(3) Looking for software in papers is time-consuming.</p>
</div>
</div>
</div>
<div class="row center">
<h4 class="header light col s12">Why does it matter?</h4>
<p class="light">Lacking better info, people often don’t use the best options, and sometimes unintentionally recreate existing tools. <strong>Time and money are wasted, reproducibility of research suffers, and funding agencies get poor return on investment</strong>.</p>
<p class="light">We believe a <strong>comprehensive software index</strong> could make it easier to find software by providing results grouped along different dimensions and containing specific details about each software resource. This would help users find software more effectively and compare alternatives more systematically.</p>
</div>
<div class="row center">
<h4 class="header light col s12">What is CASICS?</h4>
<p class="light">Software catalogs are not new, but many catalogs failed either because they were too simplistic (providing incomplete or misleading content) or relied on humans. Humans don’t scale well; <strong>automation is the only feasible way</strong> of cataloging the vast and ever-growing number of constantly-evolving software resources.</p>
<p class="light">The <em>Comprehensive and Automated Software Inventory Creation System</em> is a project to create a proof of concept. CASICS uses machine learning techniques to <strong>analyze source code</strong> in software repositories such as GitHub.</p>
</div>
<div class="row">
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">fingerprint</i></h3>
<h5 class="center light">Feature extraction from source files</h5>
<p class="light">The features are extracted from source code via language-aware parsers (for identifier names, libraries, doc strings, text strings, comments, etc.). Identifier expansion methods convert short identifiers (e.g., "readfromdb") to more meaningful strings ("read from database").</p>
</div>
</div>
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">view_quilt</i></h3>
<h5 class="center light">Ontology-based classification</h5>
<p class="light">The features are used as input into supervised, hierarchical multi-label classifiers to label software with respect to predefined ontologies. We are using a combination of <a href="https://github.com/allysonlister/swo">SWO</a>, the <a href="http://id.loc.gov">Library of Congress Subject Headings</a>, and custom ontologies.</p>
</div>
</div>
<div class="col s12 m4">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">sort</i></h3>
<h5 class="center light">Hierarchical software catalog</h5>
<p class="light">Software can be placed in a hierarchical browser organized by the ontology. Search can be augmented with ontologies to recognize when users are looking for known types of features.</p>
</div>
</div>
</div>
<div class="row center">
<h4 class="header light col s12">Learn more</h4>
<p class="light">CASICS is still a work in progress, but we have developed many software components. We have also released some as independent <strong>Python packages</strong> that we hope <strong>other projects can use</strong>.</p>
</div>
<div class="row">
<div class="col s12 m6">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">settings</i></h3>
<h5 class="center light">System architecture</h5>
<p class="light">A <a href="architecture.html">separate page</a> provides more information about the CASICS architecture, general principles, and how the different components interact with each other.</p>
</div>
</div>
<div class="col s12 m6">
<div class="icon-block">
<h3 class="center deep-teal-text"><i class="material-icons">extension</i></h3>
<h5 class="center light">Software repositories</h5>
<p class="light">We developed CASICS with modularity and reuse in mind. Our <a href="https://github.com/casics">GitHub organization</a> for CASICS holds the repositories. There you can find Python packages such as <a href="https://github.com/casics/dassie">Dassie</a> (a database of terms in the Library of Congress Subject Headings), <a href="https://github.com/casics/nostril">Nostril</a> (a nonsense string detector) and <a href="https://github.com/casics/spiral">Spiral</a> (a library for splitting identifiers found in source code). </p>
</div>
</div>
</div>
</div>
</div>
<footer class="page-footer grey">
<div class="container">
<div class="row center">
<div class="col s12 m4">
<h5 class="white-text">Project members</h5>
<ul>
<li><a class="white-text" href="http://www.cds.caltech.edu/~mhucka">Dr. Michael Hucka</a></li>
<li><a class="white-text" href="http://www.cacr.caltech.edu/~mjg">Dr. Matthew Graham</a></li>
<li><a class="white-text" href="http://www.cds.caltech.edu/~doyle">Dr. John Doyle</a></li>
</ul>
</div>
<div class="col s12 m4">
<h5 class="white-text">Support</h5>
<ul>
<li style="margin-bottom: -5px"><a class="white-text" href="https://nsf.gov"><img width="55px" src="graphics/nsf1.gif"/></a></li>
<li><a class="white-text" href="https://www.caltech.edu"><img width="120px" src="graphics/caltech-white.png"/></a></li>
</ul>
</div>
<div class="col s12 m4">
<h5 class="white-text">More information</h5>
<ul>
<li><a class="white-text" href="files/casics-poster-2016.pdf">2016 NSF meeting poster</a></li>
<li><a class="white-text" href="files/casics-poster-2017.pdf">2017 NSF meeting poster</a></li>
<li><a class="white-text" href="https://www.sciencedirect.com/science/article/pii/S0164121218300517">2018 JSS paper about survey results</a></li>
</ul>
</div>
</div>
<p class="white-text center"><small>
This material is based upon work supported by the <a class="white-text" href="https://nsf.gov"><b>National Science Foundation</b></a> under Grant Number 1533792. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.</small></p>
</div>
<div class="footer-copyright">
<div class="center container">
<small>Produced by <a class="cyan-text text-lighten-3" href="http://www.cds.caltech.edu/~mhucka/">Mike Hucka</a></small>.
<small>Page theme modified from <a class="cyan-text text-lighten-3" href="http://materializecss.com">Materialize</a></small>.
</div>
</div>
</footer>
<!-- Scripts-->
<script src="https://code.jquery.com/jquery-2.1.1.min.js"></script>
<script src="js/materialize.js"></script>
<script src="js/init.js"></script>
</body>
</html>