Swe-SE-SCI scholars: Click on a header to sort by the corresponding column.
|
Scholar |
Affiliation |
#Publ. |
SCI ratio |
1st ratio |
SSS contrib. |
SSS rating |
Apparent research interests |
Signature SSS works |
|
Claes Wohlin |
Blekinge Institute of Technology |
174 |
0.39 |
0.32 |
24.96 |
63.25 |
empirical, project, success, factors, journals, methods, analysis, reliability, literature, subjective |
2015: Towards a decision-making structure for selecting a research design in empirical software engineering. (Empirical Software Engineering)
2015: A general theory of software engineering: Balancing human, social and organizational capitals. (J. Syst. Softw.)
2013: Systematic literature reviews in software engineering. (Inf. Softw. Technol.)
2013: On the reliability of mapping studies in software engineering. (J. Syst. Softw.)
2011: Taking novelty to a new level. (Inf. Softw. Technol.)
2009: An analysis of the most cited articles in software engineering journals - 2002. (Inf. Softw. Technol.)
2008: An analysis of the most cited articles in software engineering journals - 2001. (Inf. Softw. Technol.)
2007: Most cited journal articles in software engineering. (Inf. Softw. Technol.)
2007: An analysis of the most cited articles in software engineering journals - 2000. (Inf. Softw. Technol.)
2005: Most cited journal articles in software engineering. (Inf. Softw. Technol.)
2005: An analysis of the most cited articles in software engineering journals - 1999. (Inf. Softw. Technol.)
2004: Are Individual Differences in Software Development Performance Possible to Capture Using a Quantitative Survey?. (Empirical Software Engineering)
2003: Prioritizing and Assessing Software Project Success Factors and Project Characteristics using Subjective Data. (Empirical Software Engineering)
2001: Assessing Project Success Using Subjective Evaluation Factors. (Software Quality Journal)
2000: Subjective evaluation as a tool for learning from software project success. (Inf. Softw. Technol.)
1999: Strategies for industrial relevance in software engineering education. (J. Syst. Softw.)
1995: Soft factors and their impact on time to market. (Software Quality Journal)
1995: An Experimental Evaluation of Capture-Recapture in Software Inspections. (Softw. Test. Verification Reliab.)
1994: Certification of Software Components. (IEEE Trans. Software Eng.)
|
|
Jan Bosch |
Chalmers / Gothenburg University |
329 |
0.13 |
0.31 |
12.56 |
53.03 |
product, architecture, lines, ecosystems, object, development, variability, families, design, data |
2018: Ecosystem traps and where to find them. (J. Softw. Evol. Process.)
2012: Software ecosystems: Taking software development beyond the boundaries of the organization. (J. Syst. Softw.)
2011: Introducing agile customer-centered development in a legacy software product line. (Softw., Pract. Exper.)
2010: From integration to composition: On the impact of software product lines, global development and ecosystems. (J. Syst. Softw.)
2003: Software architecture - Engineering quality attributes. (J. Syst. Softw.)
1999: Superimposition: a component adaptation technique. (Inf. Softw. Technol.)
|
|
Emilia Mendes |
Blekinge Institute of Technology |
175 |
0.18 |
0.4 |
12.64 |
38.57 |
web, effort, estimation, company, applications, value, cost, hypermedia, bayesian, improve |
2019: Using Bayesian Network to Estimate the Value of Decisions within the Context of Value-Based Software Engineering: A Multiple Case Study. (International Journal of Software Engineering and Knowledge Engineering)
2018: Towards improving decision making and estimating the value of decisions in value-based software engineering: the VALUE framework. (Software Quality Journal)
2018: Correction to: Towards improving decision making and estimating the value of decisions in value-based software engineering: the VALUE framework. (Software Quality Journal)
2008: Replicating studies on cross- vs single-company effort models using the ISBSG Database. (Empirical Software Engineering)
2008: Cross-company vs. single-company web effort models using the Tukutuku database: An extended study. (J. Syst. Softw.)
2008: Bayesian Network Models for Web Effort Prediction: A Comparative Study. (IEEE Trans. Software Eng.)
2005: Investigating Web size metrics for early Web cost estimation. (J. Syst. Softw.)
2003: A Comparative Study of Cost Estimation Models for Web Hypermedia Applications. (Empirical Software Engineering)
1998: Reusability and maintainability in hypermedia applications for education. (Inf. Softw. Technol.)
|
|
Per Runeson |
Lund University |
142 |
0.29 |
0.21 |
8.71 |
36.54 |
testing, test, inspection, unit, open, collaboration, academia, product, detection, industry |
2014: Variation factors in the design and analysis of replicated controlled experiments - Three (dis)similar studies on inspections versus unit testing. (Empirical Software Engineering)
2009: Guidelines for conducting and reporting case study research in software engineering. (Empirical Software Engineering)
2003: Test processes in software product evolution - a qualitative survey on the state of practice. (Journal of Software Maintenance)
1998: An Experimental Evaluation of an Experience-Based Capture-Recapture Method in Software Code Inspections. (Empirical Software Engineering)
|
|
Tony Gorschek |
Blekinge Institute of Technology |
112 |
0.47 |
0.12 |
11.29 |
26.69 |
requirements, model, empirical, process, product, practice, management, transfer, development, abstraction |
2014: On the use of software design models in software development practice: An empirical investigation. (J. Syst. Softw.)
2012: Introduction of a process maturity model for market-driven product management and requirements engineering. (Journal of Software Maintenance)
2008: Requirements engineering: In search of the dependent variables. (Inf. Softw. Technol.)
2007: A controlled empirical evaluation of a requirements abstraction model. (Inf. Softw. Technol.)
2006: Requirements Abstraction Model. (Requir. Eng.)
2004: Packaging software process improvement issues: a method and a case study. (Softw., Pract. Exper.)
|
|
Robert Feldt |
Chalmers / Gothenburg University |
120 |
0.3 |
0.14 |
5.34 |
26.07 |
test, search, diverse, programming, genetic, testing, cases, versions, empirical, diversity |
2010: Links between the personalities, views and attitudes of software engineers. (Inf. Softw. Technol.)
|
|
Benoit Baudry |
KTH Royal Institute of Technology |
187 |
0.14 |
0.12 |
6.1 |
24.8 |
model, test, design, testability, validation, optimization, automatic, testing, genetic, cases |
2005: Measuring design testability of a UML class diagram. (Inf. Softw. Technol.)
2005: From genetic to bacteriological algorithms for mutation-based testing. (Softw. Test. Verification Reliab.)
|
|
Björn Regnell |
Lund University |
89 |
0.34 |
0.18 |
6.29 |
23.34 |
requirements, model, quality, testing, domain, mobile, product, scenario, large, reqt |
2001: An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software. (Requir. Eng.)
2000: Are the Perspectives Really Different? - Further Experimentation on Scenario-Based Reading of Requirements. (Empirical Software Engineering)
2000: Towards integration of use case modelling and usage-based testing. (J. Syst. Softw.)
|
|
Krzysztof Wnuk |
Blekinge Institute of Technology |
92 |
0.22 |
0.3 |
7.22 |
22.21 |
requirements, management, decision, scoping, large, industrial, open, scale, visualization, innovation |
2016: Supporting Scope Tracking and Visualization for Very Large-Scale Requirements Engineering-Utilizing FSC+, Decision Patterns, and Atomic Decision Visualizations. (IEEE Trans. Software Eng.)
2015: Exploring factors affecting decision outcome and lead time in large-scale requirements engineering. (J. Softw. Evol. Process.)
2014: Bridges and barriers to hardware-dependent software ecosystem participation - A case study. (Inf. Softw. Technol.)
2013: Obsolete software requirements. (Inf. Softw. Technol.)
2012: Replication of an experiment on linguistic tool support for consolidation of requirements from multiple sources. (Empirical Software Engineering)
|
|
Michael Felderer |
Blekinge Institute of Technology |
164 |
0.1 |
0.31 |
7.58 |
21.18 |
testing, risk, security, industrial, test, system, defect, requirements, results, taxonomies |
2019: Comprehensibility of system models during test design: a controlled experiment comparing UML activity diagrams and state machines. (Software Quality Journal)
2016: Risk orientation in software testing processes of small and medium enterprises: an exploratory and comparative study. (Software Quality Journal)
2016: Model-based security testing: a taxonomy and systematic classification. (Softw. Test. Verification Reliab.)
2015: Manual test case derivation from UML activity diagrams and state machines: A controlled experiment. (Inf. Softw. Technol.)
2014: Integrating risk-based testing in industrial test processes. (Software Quality Journal)
|
|
Miroslaw Staron |
Chalmers / Gothenburg University |
124 |
0.13 |
0.36 |
9.88 |
20.48 |
measurement, industrial, development, systems, large, projects, model, measures, code, defect |
2018: Industrial experiences from evolving measurement systems into self-healing systems for improved availability. (Softw., Pract. Exper.)
2016: MeSRAM - A method for assessing robustness of measurement programs in large software development organizations and its industrial evaluation. (J. Syst. Softw.)
2012: Critical role of measures in decision processes: Managerial and technical measures in the context of large software development organizations. (Inf. Softw. Technol.)
2011: Developing measurement systems: an industrial case study. (Journal of Software Maintenance)
2010: A method for forecasting defect backlog in large streamline software development projects and its industrial evaluation. (Inf. Softw. Technol.)
2009: A framework for developing measurement systems and its industrial evaluation. (Inf. Softw. Technol.)
2008: Predicting weekly defect inflow in large software projects based on project planning and test status. (Inf. Softw. Technol.)
2006: Empirical assessment of using stereotypes to improve comprehension of UML models: A set of experiments. (J. Syst. Softw.)
|
|
Martin Monperrus |
KTH Royal Institute of Technology |
89 |
0.24 |
0.18 |
5.48 |
19.22 |
model, measurement, automatic, system, les, repair, automated, calls, detecting, generative |
2013: Automated measurement of models of requirements. (Software Quality Journal)
2013: Detecting missing method calls as violations of the majority rule. (ACM Trans. Softw. Eng. Methodol.)
2012: What should developers be aware of? An empirical study on the directives of API documentation. (Empirical Software Engineering)
|
|
Jürgen Börstler |
Blekinge Institute of Technology |
75 |
0.21 |
0.37 |
4.89 |
18.4 |
teaching, role, object, learning, play, pedagogies, tools, projects, example, programmieren |
2016: Beauty and the Beast: on the readability of object-oriented example programs. (Software Quality Journal)
2016: The Role of Method Chains and Comments in Software Readability and Comprehension - An Experiment. (IEEE Trans. Software Eng.)
1995: Integrated software reuse: Management and techniques : Paul Walton and Neil Maiden (eds) Ashgate Publishing, Hants, UK (1993) 178 pp 49.50 hardcover ISBN 1 85742 146 9. (Inf. Softw. Technol.)
|
|
Martin Höst |
Lund University |
93 |
0.18 |
0.22 |
6.96 |
17.82 |
product, processes, source, development, management, commercial, project, open, requirements, different |
2011: A systematic review of research on open source software in commercial software product development. (Inf. Softw. Technol.)
2001: Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. (J. Syst. Softw.)
2000: Using Students as Subjects-A Comparative Study of Students and Professionals in Lead-Time Impact Assessment. (Empirical Software Engineering)
2000: Evaluation of code review methods through interviews and experimentation. (J. Syst. Softw.)
1997: A subjective effort estimation experiment. (Inf. Softw. Technol.)
|
|
Daniel Méndez Fernández |
Blekinge Institute of Technology |
79 |
0.19 |
0.29 |
7.54 |
16.96 |
requirements, artefact, naming, pain, practice, results, artefacts, design, improvement, first |
2019: The open science initiative of the Empirical Software Engineering journal. (Empirical Software Engineering)
2019: Empirical software engineering: From discipline to interdiscipline. (J. Syst. Softw.)
2017: Naming the pain in requirements engineering - Contemporary problems, causes, and effects in practice. (Empirical Software Engineering)
2015: Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany. (Inf. Softw. Technol.)
2015: Artefact-based requirements engineering: the AMDiRE approach. (Requir. Eng.)
2012: Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies. (Inf. Softw. Technol.)
|
|
Mikael Svahnberg |
Blekinge Institute of Technology |
32 |
0.5 |
0.59 |
10.76 |
16.86 |
quality, architecture, architectures, method, product, requirements, attributes, building, assessment, assessing |
2017: A model for assessing and re-assessing the value of software reuse. (J. Softw. Evol. Process.)
2015: Uni-REPM: a framework for requirements engineering process assessment. (Requir. Eng.)
2013: Uni-REPM: validated and improved. (Requir. Eng.)
2010: A systematic review on strategic release planning models. (Inf. Softw. Technol.)
2007: Six years of evaluating software architectures in student projects. (J. Syst. Softw.)
2005: An Investigation of a Method for Identifying a Software Architecture Candidate with Respect to Quality Attributes. (Empirical Software Engineering)
2005: A taxonomy of variability realization techniques. (Softw., Pract. Exper.)
2004: An industrial study on building consensus around software architectures and quality attributes. (Inf. Softw. Technol.)
2003: A Quality-Driven Decision-Support Method for Identifying Software Architecture Candidates. (International Journal of Software Engineering and Knowledge Engineering)
1999: Evolution in software product lines: two cases. (Journal of Software Maintenance)
|
|
Ivica Crnkovic |
Chalmers / Gothenburg University |
144 |
0.09 |
0.28 |
5.31 |
16.75 |
component, systems, development, process, scm, embedded, components, model, management, predictability |
2011: A Classification Framework for Software Component Models. (IEEE Trans. Software Eng.)
2005: Automated Component-Based Software Engineering. (J. Syst. Softw.)
2002: Challenges of component-based development. (J. Syst. Softw.)
|
|
Darja Smite |
Blekinge Institute of Technology |
68 |
0.18 |
0.49 |
6.26 |
15.51 |
global, development, learned, lessons, coordination, empirical, evidence, product, offshoring, project |
2017: Software teams and their knowledge networks in large-scale software development. (Inf. Softw. Technol.)
2014: An empirically based terminology and taxonomy for global software engineering. (Empirical Software Engineering)
2013: Offshore insourcing in software development: Structuring the decision-making process. (J. Syst. Softw.)
2012: Lessons learned from transferring software products to India. (J. Softw. Evol. Process.)
2010: Empirical evidence in global software engineering: a systematic review. (Empirical Software Engineering)
|
|
Efi Papatheocharous |
RISE Research Institutes of Sweden AB |
51 |
0.2 |
0.51 |
5.01 |
12.79 |
cost, estimation, decision, artificial, networks, neural, development, fuzzy, systems, agile |
2018: The GRADE taxonomy for supporting decision-making of asset selection in software-intensive system development. (Inf. Softw. Technol.)
2017: An investigation of effort distribution among development phases: A four-stage progressive software cost estimation model. (J. Softw. Evol. Process.)
2014: Empirical evidence and state of practice of software agile teams. (J. Softw. Evol. Process.)
2012: A Hybrid Software Cost Estimation Approach Utilizing Decision Trees and Fuzzy Logic. (International Journal of Software Engineering and Knowledge Engineering)
|
|
Eric Knauss |
Chalmers / Gothenburg University |
97 |
0.1 |
0.32 |
3.67 |
12.58 |
requirements, continuous, supporting, von, ecosystems, system, heuristic, clarification, feedback, anforderungen |
2018: Continuous clarification and emergent requirements flows in open-commercial software ecosystems. (Requir. Eng.)
2015: Patterns of continuous requirements clarification. (Requir. Eng.)
|
|
Richard Torkar |
Chalmers / Gothenburg University |
63 |
0.35 |
0.1 |
3.51 |
12.03 |
testing, systematic, purpose, patterns, partition, requirements, extracting, unit, reuse, creation |
2012: Requirements Traceability: a Systematic Review and Industry Case Study. (International Journal of Software Engineering and Knowledge Engineering)
|
|
Patrizio Pelliccione |
Chalmers / Gothenburg University |
128 |
0.13 |
0.06 |
4.61 |
11.98 |
systems, cars, specifications, architectural, framework, connected, evolving, testor, architecture, beyond |
2009: CHARMY: A Framework for Designing and Verifying Architectural Specifications. (IEEE Trans. Software Eng.)
2008: An architectural approach to the correct and automatic assembly of evolving component-based systems. (J. Syst. Softw.)
|
|
Wasif Afzal |
Mälardalen University |
59 |
0.19 |
0.22 |
6.08 |
11.74 |
runtime, systematic, fault, testing, model, megam, programming, complex, framework, genetic |
2016: Software test process improvement approaches: A systematic literature review and an industrial case study. (J. Syst. Softw.)
2015: An experiment on the effectiveness and efficiency of exploratory testing. (Empirical Software Engineering)
2014: Prediction of faults-slip-through in large software projects: an empirical evaluation. (Software Quality Journal)
2012: Resampling Methods in Software Quality Classification. (International Journal of Software Engineering and Knowledge Engineering)
2009: A systematic review of search-based testing for non-functional system properties. (Inf. Softw. Technol.)
|
|
Markus Borg |
RISE Research Institutes of Sweden AB |
57 |
0.16 |
0.44 |
4.98 |
11.58 |
traceability, reports, impact, analysis, context, issue, time, recovery, bug, information |
2019: Selecting component sourcing options: A survey of software engineering's broader make-or-buy decisions. (Inf. Softw. Technol.)
2017: Supporting Change Impact Analysis Using a Recommendation System: An Industrial Case Study in a Safety-Critical Context. (IEEE Trans. Software Eng.)
2016: TuneR: a framework for tuning software engineering tools with hands-on instructions in R. (J. Softw. Evol. Process.)
2014: Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability. (Empirical Software Engineering)
|
|
Gregory Gay |
Chalmers / Gothenburg University |
30 |
0.3 |
0.67 |
6.51 |
11.03 |
test, generation, real, search, coverage, model, fitness, program, steering, automated |
2017: Automated Steering of Model-Based Test Oracles to Admit Real Program Behaviors. (IEEE Trans. Software Eng.)
2016: The Effect of Program and Model Structure on the Effectiveness of MC/DC Test Adequacy Coverage. (ACM Trans. Softw. Eng. Methodol.)
2015: The Risks of Coverage-Directed Test Case Generation. (IEEE Trans. Software Eng.)
2015: Automated Oracle Data Selection Support. (IEEE Trans. Software Eng.)
2010: Finding robust solutions in requirements models. (Autom. Softw. Eng.)
2010: Automatically finding the control variables for complex system behavior. (Autom. Softw. Eng.)
|
|
Richard Berntsson-Svensson |
Chalmers / Gothenburg University |
43 |
0.21 |
0.44 |
4.84 |
10.94 |
requirements, quality, quper, practice, industrial, creativity, model, companies, techniques, release |
2017: Is role playing in Requirements Engineering Education increasing learning outcome? (Requir. Eng.)
2013: An investigation of how quality requirements are specified in industrial practice. (Inf. Softw. Technol.)
2012: Setting quality targets for coming releases with QUPER: an industrial case study. (Requir. Eng.)
2012: Quality Requirements in Industrial Practice - An Extended Interview Study at Eleven Companies. (IEEE Trans. Software Eng.)
|
|
Emelie Engström |
Lund University |
31 |
0.32 |
0.39 |
4.81 |
10.55 |
test, regression, testing, selection, line, product, systematic, empirical, taxonomy, mapping |
2017: SERP-test: a taxonomy for supporting industry-academia communication. (Software Quality Journal)
2013: Test overlay in an emerging software product line - An industrial case study. (Inf. Softw. Technol.)
2011: Software product line testing - A systematic mapping study. (Inf. Softw. Technol.)
2010: A systematic review on regression test selection techniques. (Inf. Softw. Technol.)
|
|
Michael Unterkalmsteiner |
Blekinge Institute of Technology |
32 |
0.34 |
0.28 |
5.81 |
10.15 |
requirements, process, alignment, test, improvement, expert, systematic, taxonomy, quality, literature |
2016: Large-scale information retrieval in software engineering - an experience report from industrial application. (Empirical Software Engineering)
2015: Assessing requirements engineering and software test alignment - Five case studies. (J. Syst. Softw.)
2014: A conceptual framework for SPI evaluation. (J. Softw. Evol. Process.)
2014: A taxonomy for requirements engineering and software test alignment. (ACM Trans. Softw. Eng. Methodol.)
2012: Evaluation and Measurement of Software Process Improvement - A Systematic Literature Review. (IEEE Trans. Software Eng.)
|
|
Nauman Bin Ali |
Blekinge Institute of Technology |
21 |
0.48 |
0.48 |
6.51 |
10.08 |
systematic, process, simulation, literature, search, industrial, reviews, stream, value, mapping |
2019: On the search for industry-relevant regression testing research. (Empirical Software Engineering)
2019: A critical appraisal tool for systematic literature reviews in software engineering. (Inf. Softw. Technol.)
2018: Reliability of search in systematic reviews: Towards a quality assessment framework for the automated-search strategy. (Inf. Softw. Technol.)
2016: FLOW-assisted value stream mapping in the early phases of large-scale software development. (J. Syst. Softw.)
2015: Evaluation of simulation-assisted value stream mapping for software product development: Two industrial cases. (Inf. Softw. Technol.)
2014: A systematic literature review on the industrial use of software process simulation. (J. Syst. Softw.)
|
|
Björn Lundell |
Skövde University |
71 |
0.1 |
0.31 |
3.14 |
9.17 |
open, source, tool, perceptions, method, swedish, standards, openness, experiences, companies |
2011: Practitioner perceptions of Open Source software in the embedded systems area. (J. Syst. Softw.)
2004: Changing perceptions of CASE technology. (J. Syst. Softw.)
|
|
Elizabeth Bjarnason |
Lund University |
30 |
0.23 |
0.7 |
6.33 |
8.89 |
requirements, distances, development, evidence, gaps, communication, timelines, cases, method, project |
2019: Improving requirements-test alignment by prescribing practices that mitigate communication gaps. (Empirical Software Engineering)
2017: The role of distances in requirements communication: a case study. (Requir. Eng.)
2016: A theory of distances in software engineering. (Inf. Softw. Technol.)
2016: A multi-case study of agile requirements engineering and the use of test cases as requirements. (Inf. Softw. Technol.)
2014: Challenges and practices in aligning requirements with verification and validation: a case study of six companies. (Empirical Software Engineering)
2012: Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering. (Inf. Softw. Technol.)
|
|
Regina Hebig |
Chalmers / Gothenburg University |
57 |
0.12 |
0.33 |
3.0 |
8.68 |
model, development, evolution, mde, languages, processes, coding, impact, process, combined |
2017: The changing balance of technology and process: A case study on a combined setting of model-driven development and classical C coding. (J. Softw. Evol. Process.)
2017: Approaches to Co-Evolution of Metamodels and Models: A Survey. (IEEE Trans. Software Eng.)
|
|
Fabian Fagerholm |
Blekinge Institute of Technology |
41 |
0.17 |
0.39 |
3.74 |
8.58 |
agile, projects, education, experience, patterns, performance, continuous, source, onboarding, open |
2018: Designing and implementing an environment for software start-up education: Patterns and anti-patterns. (J. Syst. Softw.)
2017: The RIGHT model for Continuous Experimentation. (J. Syst. Softw.)
2015: Performance Alignment Work: How software developers experience the continuous adaptation of team performance in Lean and Agile environments. (Inf. Softw. Technol.)
|
|
Davide Fucci |
Blekinge Institute of Technology |
41 |
0.17 |
0.39 |
4.64 |
8.58 |
test, development, replication, effects, impact, requirements, conformance, process, external, first |
2020: Need for Sleep: The Impact of a Night of Sleep Deprivation on Novice Developers' Performance. (IEEE Trans. Software Eng.)
2017: A Dissection of the Test-Driven Development Process: Does It Really Matter to Test-First or to Test-Last? (IEEE Trans. Software Eng.)
2015: Towards an operationalization of test-driven development skills: An industrial empirical study. (Inf. Softw. Technol.)
2014: On the role of tests in test-driven development: a differentiated and partial replication. (Empirical Software Engineering)
|
|
Philipp Leitner |
Chalmers / Gothenburg University |
115 |
0.05 |
0.23 |
2.59 |
7.78 |
service, services, cloud, level, violations, web, practice, compositions, testing, performance |
2019: A mixed-method empirical study of Function-as-a-Service software development in industrial practice. (J. Syst. Softw.)
|
|
Pontus Johnson |
KTH Royal Institute of Technology |
90 |
0.06 |
0.26 |
2.25 |
7.26 |
architecture, analysis, modeling, theory, probabilistic, enterprise, general, business, extended, influence |
2016: The Tarpit - A general theory of software engineering. (Inf. Softw. Technol.)
|
|
Birgit Penzenstadler |
Chalmers / Gothenburg University |
102 |
0.05 |
0.42 |
2.37 |
7.22 |
sustainability, requirements, systems, model, design, domain, system, green, automotive, systematic |
2018: Sustainability analysis and ease of learning in artifact-based requirements engineering: The newest member of the family of studies (It's a girl!). (Inf. Softw. Technol.)
|
|
Welf Löwe |
Linneaus Univerity |
111 |
0.05 |
0.16 |
2.55 |
7.2 |
programs, logp, machines, graphs, task, optimization, scheduling, pram, communication, machine |
2005: Rapid Construction of Software Comprehension Tools. (International Journal of Software Engineering and Knowledge Engineering)
|
|
Riccardo Scandariato |
Chalmers / Gothenburg University |
66 |
0.09 |
0.17 |
3.0 |
7.05 |
security, design, architecture, system, microsoft, least, assessment, modeling, learned, testing |
2015: A descriptive study of Microsoft's threat modeling technique. (Requir. Eng.)
2014: Predicting Vulnerable Software Components via Text Mining. (IEEE Trans. Software Eng.)
|
|
Panagiota Chatzipetrou |
Örebro University |
18 |
0.33 |
0.56 |
2.52 |
6.88 |
analysis, statistical, framework, requirements, data, phase, distribution, effort, goals, quality |
2015: A multivariate statistical framework for the analysis of software effort phase distribution. (Inf. Softw. Technol.)
2015: An experience-based framework for evaluating alignment of software quality goals. (Software Quality Journal)
|
|
Bestoun S. Ahmed |
Karlstad University |
22 |
0.27 |
0.45 |
4.36 |
6.85 |
testing, interaction, combinatorial, particle, swarm, model, strength, applications, aware, test |
2019: Code-aware combinatorial interaction testing. (IET Software)
2017: Handling constraints in combinatorial interaction testing in the presence of multi objective particle swarm and multithreading. (Inf. Softw. Technol.)
2015: Achievement of minimized combinatorial test suite for configuration-aware software functional testing using the Cuckoo Search algorithm. (Inf. Softw. Technol.)
2011: A variable strength interaction test suites generation strategy using Particle Swarm Optimization. (J. Syst. Softw.)
|
|
Jakob Axelsson |
RISE Research Institutes of Sweden AB |
61 |
0.08 |
0.57 |
2.86 |
6.84 |
systems, system, time, real, embedded, analysis, automotive, architecting, hardware, literature |
2016: Quality assurance in software ecosystems: A systematic literature mapping and research agenda. (J. Syst. Softw.)
2014: Characteristics of software ecosystems for Federated Embedded Systems: A case study. (Inf. Softw. Technol.)
|
|
Jennifer Horkoff |
Chalmers / Gothenburg University |
96 |
0.05 |
0.39 |
5.01 |
6.77 |
goal, modeling, requirements, analysis, interactive, models, model, systematic, creative, experiences |
2019: Creative goal modeling for innovative requirements. (Inf. Softw. Technol.)
2019: Goal-oriented requirements engineering: an extended systematic mapping study. (Requir. Eng.)
2016: Interactive goal model analysis for early requirements engineering. (Requir. Eng.)
2013: Comparison and evaluation of goal-oriented satisfaction analysis techniques. (Requir. Eng.)
|
|
Peter Fritzson |
Linköping University |
123 |
0.04 |
0.2 |
3.48 |
6.71 |
modeling, language, modelica, object, equation, debugging, environment, system, incremental, physical |
1994: Using assertions in declarative and operational models for automated debugging. (J. Syst. Softw.)
1983: Symbolic debugging through incremental compilation in an integrated environment. (J. Syst. Softw.)
|
|
Emil Alégroth |
Blekinge Institute of Technology |
26 |
0.19 |
0.54 |
3.41 |
6.3 |
testing, gui, visual, industrial, practice, empirical, test, system, technical, testware |
2017: On the long-term use of visual gui testing in industrial practice: a case study. (Empirical Software Engineering)
2016: Maintenance of automated test suites in industry: An empirical study on Visual GUI Testing. (Inf. Softw. Technol.)
2015: Visual GUI testing in practice: challenges, problemsand limitations. (Empirical Software Engineering)
|
|
Thorsten Berger |
Chalmers / Gothenburg University |
77 |
0.06 |
0.21 |
3.02 |
6.06 |
variability, modeling, feature, systems, efficiency, und, editing, management, large, domain |
2014: Variability mechanisms in software ecosystems. (Inf. Softw. Technol.)
2013: A Study of Variability Models and Languages in the Systems Software Domain. (IEEE Trans. Software Eng.)
|
|
Jan-Philipp Steghöfer |
Chalmers / Gothenburg University |
69 |
0.06 |
0.28 |
1.95 |
5.61 |
systems, self, open, organising, agile, die, organic, scrum, computing, change |
2017: No silver brick: Opportunities and limitations of teaching Scrum with Lego workshops. (J. Syst. Softw.)
|
|
Federico Ciccozzi |
Mälardalen University |
65 |
0.06 |
0.45 |
3.71 |
5.48 |
systems, model, uml, embedded, models, code, modelling, generation, execution, trip |
2018: Architecture optimization: speed or accuracy? both! (Software Quality Journal)
2016: Explicit connection patterns (ECP) profile and semantics for modelling and generating explicit connections in complex UML composite structures. (J. Syst. Softw.)
2013: Round-trip support for extra-functional property management in model-driven engineering of embedded systems. (Inf. Softw. Technol.)
|
|
Helena Holmström Olsson |
Malmö University |
93 |
0.04 |
0.32 |
2.19 |
5.25 |
ecosystem, data, empowerment, make, paying, strategic, online, strategy, mind, model |
2017: From ad hoc to strategic ecosystem management: the "Three-Layer Ecosystem Strategy Model" (TeLESM). (J. Softw. Evol. Process.)
|
|
Robert Lagerström |
KTH Royal Institute of Technology |
74 |
0.05 |
0.27 |
4.7 |
5.08 |
architecture, enterprise, systems, analysis, modifiability, cost, management, change, design, measuring |
2013: Increasing software development efficiency and maintainability for complex industrial systems - A case study. (J. Softw. Evol. Process.)
2012: Identifying factors affecting software development cost and productivity. (Software Quality Journal)
2010: Architecture analysis of enterprise systems modifiability - Models, analysis, and validation. (J. Syst. Softw.)
2010: Architecture analysis of enterprise systems modifiability: a metamodel for software change cost estimation. (Software Quality Journal)
|
|
Hannes Holm |
KTH Royal Institute of Technology |
39 |
0.08 |
0.54 |
1.56 |
4.36 |
attacks, vulnerability, system, expert, empirical, application, web, scanning, investigation, security |
2015: A Bayesian network model for likelihood estimations of acquirement of critical software vulnerabilities and exploits. (Inf. Softw. Technol.)
|
|
Thomas Olsson |
RISE Research Institutes of Sweden AB |
39 |
0.08 |
0.33 |
1.56 |
4.17 |
requirements, companies, gqm, language, time, reconfigurable, quality, decision, making, testing |
2019: An empirical study on decision making for quality requirements. (J. Syst. Softw.)
|
|
Imed Hammouda |
Chalmers / Gothenburg University |
73 |
0.04 |
0.32 |
2.8 |
4.12 |
open, source, concern, design, patterns, pattern, development, tool, learning, communities |
2011: Managing Concern Knowledge in Software Systems. (International Journal of Software Engineering and Knowledge Engineering)
2009: Design profiles: toward unified tool support for design patterns and UML profiles. (Softw., Pract. Exper.)
|
|
Ludwik Kuzniarz |
Blekinge Institute of Technology |
27 |
0.11 |
0.56 |
1.44 |
4.06 |
uml, model, models, multimedia, teaching, development, modeling, stereotypes, domain, ontologies |
2011: Empirical extension of a classification framework for addressing consistency in model based development. (Inf. Softw. Technol.)
|
|
Francis Palma |
Linneaus Univerity |
20 |
0.15 |
0.7 |
1.37 |
4.06 |
antipatterns, detection, specification, patterns, soa, apis, service, process, linguistic, test |
2019: UniDoSA: The Unified Specification and Detection of Service Antipatterns. (IEEE Trans. Software Eng.)
|
|
Gul Calikli |
Chalmers / Gothenburg University |
26 |
0.12 |
0.38 |
1.43 |
4.04 |
confirmation, bias, effects, analysis, defect, experience, modeling, aspects, factors, company |
2015: Empirical analysis of factors affecting confirmation bias levels of software engineers. (Software Quality Journal)
|
|
Jonas Lundberg |
Linneaus Univerity |
58 |
0.05 |
0.29 |
1.75 |
4.0 |
analysis, design, response, resilience, points, identification, management, work, traffic, designing |
2009: Fast and precise points-to analysis. (Inf. Softw. Technol.)
|
|
Jonas Gamalielsson |
Skövde University |
32 |
0.09 |
0.5 |
2.39 |
3.96 |
open, source, standards, biological, fork, model, communities, pathways, semantic, pdf |
2015: On organisational influences in software standards and their open source implementations. (Inf. Softw. Technol.)
2014: Sustainability of Open Source software communities beyond a fork: How and why has the LibreOffice project evolved? (J. Syst. Softw.)
|
|
Ulrik Franke |
RISE Research Institutes of Sweden AB |
69 |
0.04 |
0.38 |
1.86 |
3.93 |
enterprise, architecture, insurance, service, cyber, analysis, framework, availability, decision, models |
2012: Availability of enterprise IT systems: an expert-based Bayesian framework. (Software Quality Journal)
|
|
Mariam Kamkar |
Linköping University |
27 |
0.11 |
0.41 |
2.34 |
3.93 |
slicing, dynamic, interprocedural, programs, program, debugging, applied, testing, algorithmic, flow |
1998: Application of program slicing in algorithmic debugging. (Inf. Softw. Technol.)
1995: An overview and comparative classification of program slicing techniques. (J. Syst. Softw.)
|
|
Muhammad Ovais Ahmad |
Karlstad University |
16 |
0.19 |
0.56 |
2.23 |
3.9 |
kanban, development, agile, systematic, companies, benefits, greenfield, preliminary, perceptions, analysis |
2018: Kanban in software engineering: A systematic mapping study. (J. Syst. Softw.)
2017: An empirical study of portfolio management and Kanban in agile and lean software companies. (J. Softw. Evol. Process.)
|
|
Kenneth Lind |
Chalmers / Gothenburg University |
12 |
0.25 |
0.75 |
1.29 |
3.86 |
size, estimation, components, embedded, real, code, automated, time, compsize, model |
2012: A Practical Approach to Size Estimation of Embedded Software Components. (IEEE Trans. Software Eng.)
|
|
Deepika Badampudi |
Blekinge Institute of Technology |
11 |
0.27 |
0.82 |
2.18 |
3.83 |
knowledge, translation, systematic, decision, literature, making, publications, considerations, bayesian, reporting |
2018: A decision-making process-line for selection of software asset origins and components. (J. Syst. Softw.)
2016: Software component decision-making: In-house, OSS, COTS or outsourcing - A systematic literature review. (J. Syst. Softw.)
|
|
Birgitta Lindström |
Skövde University |
19 |
0.16 |
0.42 |
2.26 |
3.83 |
mutation, time, mutants, subsuming, testability, aspect, strong, real, test, dynamic |
2019: On strong mutation and the theory of subsuming logic-based mutants. (Softw. Test. Verification Reliab.)
2017: Using mutation to design tests for aspect-oriented models. (Inf. Softw. Technol.)
|
|
Javier Gonzalez-Huerta |
Blekinge Institute of Technology |
34 |
0.09 |
0.18 |
1.51 |
3.67 |
architecture, derivation, product, model, validating, multimodel, improvement, models, bpmn, automatic |
2015: Validating a model-driven software architecture evaluation and improvement method: A family of experiments. (Inf. Softw. Technol.)
|
|
Ana Magazinius |
RISE Research Institutes of Sweden AB |
8 |
0.38 |
0.75 |
2.15 |
3.64 |
cost, estimation, distortions, feature, distortional, organizational, context, practice, aspects, inhibitors |
2012: Investigating intentional distortions in software cost estimation - An exploratory study. (J. Syst. Softw.)
2010: Software cost estimation inhibitors - a case study in automotive context. (Journal of Software Maintenance)
|
|
Kristian Sandahl |
Linköping University |
28 |
0.21 |
0.07 |
1.72 |
3.53 |
expert, requirements, inspections, participation, assessing, replication, methods, developing, systems, active |
1998: An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections. (Empirical Software Engineering)
|
|
Patrik Berander |
Malmö University |
7 |
0.43 |
0.71 |
2.14 |
3.47 |
requirements, hierarchical, cumulative, prioritization, hierarchies, voting, metric, key, process, subjects |
2009: Evaluating two ways of calculating priorities in requirements hierarchies - An experiment on hierarchical cumulative voting. (J. Syst. Softw.)
2006: Hierarchical Cumulative Voting (hcv) - Prioritization of Requirements in Hierarchies. (International Journal of Software Engineering and Knowledge Engineering)
|
|
Pasqualina Potena |
RISE Research Institutes of Sweden AB |
32 |
0.09 |
0.16 |
1.49 |
3.37 |
tradeoff, composition, architecture, service, attributes, quality, directions, optimization, systems, functional |
2013: Optimization of adaptation plans for a service-oriented architecture with cost, reliability, availability and performance tradeoff. (J. Syst. Softw.)
|
|
Görel Hedin |
Lund University |
76 |
0.03 |
0.26 |
1.84 |
3.23 |
attribute, grammars, programming, extreme, preface, object, jastadd, language, system, incremental |
2005: Teaching extreme programming to large groups of students. (J. Syst. Softw.)
|
|
Niklas Lavesson |
Jönköping University |
54 |
0.04 |
0.24 |
1.62 |
2.99 |
learning, end, user, agreements, license, spyware, metric, online, impact, assessment |
2014: A method for evaluation of learning components. (Autom. Softw. Eng.)
|
|
Narges Khakpour |
Linneaus Univerity |
19 |
0.11 |
0.79 |
1.27 |
2.93 |
systems, self, adaptive, formal, behavioral, control, policies, adaptation, policy, analysis |
2012: HPobSAM for modeling and analyzing IT Ecosystems - Through a case study. (J. Syst. Softw.)
|
|
Lars Pareto |
Chalmers / Gothenburg University |
26 |
0.08 |
0.35 |
1.34 |
2.8 |
architectural, concern, model, empirical, station, base, projects, design, concerns, investigation |
2012: Collaborative prioritization of architectural concerns. (J. Syst. Softw.)
|
|
Christin Lindholm |
Lund University |
8 |
0.25 |
0.75 |
2.06 |
2.57 |
risk, development, device, analysis, medical, management, process, investigated, planning, user |
2015: Involving user perspective in a software risk management process. (J. Softw. Evol. Process.)
2014: A case study on software risk analysis and planning in medical device development. (Software Quality Journal)
|
|
Michael Mattsson |
Blekinge Institute of Technology |
13 |
0.15 |
0.54 |
1.21 |
2.57 |
framework, industrial, evolving, experience, causes, stability, evolution, frameworks, paper, solutions |
2000: Stability assessment of evolving industrial object-oriented frameworks. (Journal of Software Maintenance)
|
|
Francisco Gomes de Oliveira Neto |
Chalmers / Gothenburg University |
13 |
0.15 |
0.54 |
2.11 |
2.57 |
test, requirements, testing, support, empirical, fault, automatic, writing, reproducibility, automotive |
2019: Evolution of statistical analysis in empirical software engineering research: Current state and steps forward. (J. Syst. Softw.)
2016: Full modification coverage through automatic similarity-based test case selection. (Inf. Softw. Technol.)
|
|
Jelena Zdravkovic |
Stockholm University |
87 |
0.02 |
0.28 |
1.95 |
2.52 |
business, capability, modeling, requirements, service, processes, organizations, services, enterprise, process |
2015: Capturing consumer preferences as requirements for software product lines. (Requir. Eng.)
|
|
Cyrille Artho |
KTH Royal Institute of Technology |
85 |
0.02 |
0.55 |
1.93 |
2.5 |
model, checking, testing, analysis, networked, java, static, test, applications, techniques |
2003: High-level data races. (Softw. Test. Verification Reliab.)
|
|
Saad Mubeen |
Mälardalen University |
64 |
0.02 |
0.62 |
1.63 |
1.89 |
analysis, time, systems, end, response, embedded, timing, component, distributed, vehicular |
2015: Integrating mixed transmission and practical limitations with the worst-case response-time analysis for Controller Area Network. (J. Syst. Softw.)
|
|
Niklas Mellegård |
RISE Research Institutes of Sweden AB |
12 |
0.08 |
0.67 |
1.11 |
1.36 |
defect, automotive, light, efficiency, impact, process, classification, scheme, embedded, improving |
2016: Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study. (IEEE Trans. Software Eng.)
|
|
Daniel Flemström |
Mälardalen University |
8 |
0.12 |
0.75 |
1.07 |
1.33 |
test, interactive, guarded, assertions, passive, language, systematic, systems, system, requirements |
2018: Similarity-based prioritization of test case automation. (Software Quality Journal)
|
|
Peter Wallin |
RISE Research Institutes of Sweden AB |
11 |
0.09 |
0.27 |
1.1 |
1.27 |
issues, system, development, related, mitigation, architecture, architecting, architectures, heavy, vehicles |
2012: Problems and their mitigation in system and software architecting. (Inf. Softw. Technol.)
|
|
Francesco Flammini |
Linneaus Univerity |
42 |
0.02 |
0.43 |
1.41 |
1.23 |
systems, critical, surveillance, security, modelling, infrastructures, multiformalism, infrastructure, physical, model |
2009: Automatic instantiation of abstract tests on specific configurations for large critical control systems. (Softw. Test. Verification Reliab.)
|
|
Stefan Cedergren |
RISE Research Institutes of Sweden AB |
4 |
0.25 |
0.25 |
1.03 |
1.0 |
performance, development, products, evaluating |
2014: Evaluating performance in the development of software-intensive products. (Inf. Softw. Technol.)
|


TRINITY_RNASEQ_ROOT/Analysis/Coding/transcripts_to_best_scoring_ORFs.pl
Likely coding regions can be extracted from Trinity transcripts using a set of utilities included in the Trinity software distribution. The system works as follows:
the longest ORF is identified within the Trinity transcript (if strand-specific, this is restricted to the top strand).
of all the longest ORFs extracted, a subset corresponding to the very longest ones (and most likely to be genuine) are identified and used to parameterize a Markov model based on hexamers. These likely coding sequences are randomized to provide a sequence composition corresponding to non-coding sequence.
all longest ORFs found are scored according to the Markov Model (log likelihood ratio based on coding/noncoding) in each of the six possible reading frames. If the putative ORF proper coding frame scores positive and is highest of the other presumed wrong reading frames, then that ORF is reported.
if a high-scoring ORF is eclipsed by (fully contained within the span of) a longer ORF in a different reading frame, it is excluded.
The scoring of ORFs is largely based on that described for GeneID, and the ORF selection process was added here.
Extracting likely coding regions from Trinity transcripts can be done using:
TRINITY_RNASEQ_ROOT/Analysis/Coding/transcripts_to_best_scoring_ORFs.pl
with options:
############################# Options ################################################### # # Required: # # -t transcripts.fasta # # Optional: # # -m minimum protein length (default: 100) # # -G genetic code (default: universal, options: Euplotes, Tetrahymena, Candida, Acetabularia) # # -h print this option menu and quit # -v verbose # # -C complete ORFs only ******** # -S strand-specific (only analyzes top strand, set this for strand-specific data) # -T top longest ORFs to train Markov Model (hexamer stats) (default: 500) # ##############################################################################################
Sample data and example execution are provided at
TRINITY_RNASEQ_ROOT/sample_data/test_Trinity_Coding_Extraction
Just run runMe.sh to run the process.
The process involves
Final output files include:
best_candidates.eclipsed_orfs_removed.cds best_candidates.eclipsed_orfs_removed.pep best_candidates.eclipsed_orfs_removed.gff3 best_candidates.eclipsed_orfs_removed.bed
The .bed file can be loaded into IGV for viewing along with the additional Trinity assembly and alignment data.


PICS: Special screening of the new RapMan film Blue Story at Cineworld Parnell Street
by Kendra BeckerWell-known faces stepped out at Dublin’s Cineworld for the special preview screening of Blue Story.
The film tells the story of best friends Timmy and Marco, who live in different London boroughs.
That’s until Marco is beaten up by one of Timmy’s friends, and the pair are drawn into a gang war where your postcode decides which side you’re on.
Rapman, real name Andrew Onwubolu, directs this British drama about the effects of gang violence in London, starring Stephen Odubola, Michael Ward and Karla-Simone Spence.


{{{modal.message}}}
Enter the ID of the user you want to own the recording or leave blank for nobody
{{#if userPic}} {{/if}}{{userName}}


The idea was born at an weekend of working together at Break The Block, a blockchain in insurance hackathon. We had fun hacking and we created My Claim Dossier which won ‘Best Blockchain’ and ‘Best Concept’ at Break The Block.
My Claim Dossier is built on a concept of distributed ledger architecture that can retain any customer’s full claims history. This enables insurers to create fairer alternative pricing strategies and allow customers to shop for better quotes without incurring the administrative costs that rigorous screening measures entail. We believe that with My Claim Dossier, that smaller insurers could club together to cut costs of storing information on a large customer database.
We are a team of two developers, Jaycee Cheong & Caroline Clark. We owe our success to Rosi Kepes, our finance/economics expert and Quynh Nhim Kovacs, our mentor.


| Methods' Summary |
| getLayer |
retrieves the layer data for a component, if newer than indicated.
|
| getUpdatableLayer |
retrieves a writable representation of the layer for a component.
|
| Methods' Details |
getLayer
- Description
- retrieves the layer data for a component, if newer than indicated.
A timestamp can be provided, which is used to indicate
a point in time. The layer should be returned only if is modified
since that time.
- Parameter aComponent
- The name of the component to access.
- Parameter aTimestamp
- a timestamp for the layer.
An empty timestamp indicates, that the layer should be
retrieved irrespective of its modification time.
The format and meaning of a timestamp depends on
the implementation. Timestamps can be obtained using
::com::sun::star::util::XTimeStamped::getTimestamp().
- Returns
- a Layer object providing access to the layer data,
NULL if the layer is newer than indicated by the timestamp.
- Throws
- com::sun::star::lang::IllegalArgumentException
if the component identifier is invalid or
if the timestamp is invalid.
- Throws
- com::sun::star::configuration::backend::BackendAccessException
if an error occurs while accessing the data.
- See also
- ::com::sun::star::util::XTimeStamped
|
|
getUpdatableLayer
- Description
- retrieves a writable representation of the layer for a component.
- Parameter aComponent
- The name of the component to access.
- Returns
- an UpdatableLayer object providing
write access to the layer
- Throws
- com::sun::star::lang::IllegalArgumentException
if the component identifier is invalid.
- Throws
- com::sun::star::lang::NoSupportException
if the implementation does not support updates.
- Throws
- com::sun::star::configuration::backend::BackendAccessException
if an error occurs while accessing the data.
|
|
Top of Page
Copyright © 2013, The Apache Software Foundation, Licensed under the Apache License, Version 2.0. Apache, the Apache feather logo, Apache OpenOffice and OpenOffice.org are trademarks of The Apache Software Foundation. Other names may be trademarks of their respective owners.


{% extends 'home/base.html'%} {% block content%}
With this app, users can learn and understand techniques and skills straight from trainers experiences online and users will be able to upload a video about how they train and develop their body to either get feedback about how to improve and what is wrong or to teach other users about the correct way to train your body and when to prevent wrong exercises.
You will be able to get help by experts from various sports such as volleyball, soccer, baseball for users to get help or teach from.


Sufiyan Rajapatel
I'm an Annovative Design Thinker
Designer
3D Modeling Designer, Cswa, User of Advance Manufacturing Techniques.
AboutMe
Hie! This IS Sufiyan Nice to Meet You!
Pursuing Engineering in Mechanical.Experienced with all stages of Mechanical Design and Analysis of the system. well-versed in numerous Technical software and programing Languages including Catia, SolidWorks, C Programming, Python.Strong background in Mechanical Design, Project Management.
OurServices
Provide the Design Of Concepts from A to Z for your seamless work flow with best aesthetics and ergonomics of product
"You Think, We Create"
Mechanical Design
The design give us ability to model the things under the different circumstances by applying the knowledge of mechanical design.
Software Modelling
Thhe Software Modeling give us ablity to conceptualize the design.
Additive Manufacturing
It is new technique to manufacture things and can use to print Complex Geometries.
Automation Solutions
Mechanical Engineering for Industrial Automation. Industrial automation solutions help in monitoring and controlling these processes. Improving quality, production efficiency and reducing overall costs are the other goals of industrial automation.
CAD/CAM Solutions
CAD stands for Computer Aided Design and CAM stands for Computer Aided Manufacturing, thus the term CAD/CAM implies that an engineer can use computer system for designing and controlling the manufacturing process of mechanical devices.
Hardware And Software Works
I am able to install any of software and hardware in computer to work seamlessly.
I Am Available For Freelancer.
Provide the Design Of Concepts from A to Z for your seamless work flow with best aesthetics and ergonomics of product
"You Think, We Create"
Contact me.
AimWorks
Dream that inspires me and raise me high.
WorksWith
Provide the Design Of Concepts from A to Z for your seamless work flow with best aesthetics and ergonomics of product
"You Think, We Create"
ContactUs
Provide the Design Of Concepts from A to Z for your seamless work flow with best aesthetics and ergonomics of product


Death of a Sailor: A Novel History of Murder in 1830s New York, War and Forbidden Love in the Age of Napoleon, and Captivity and Freedom in the Last Days of the Atlantic Slave Trade; in many, many Parts.
“Identity?” said Jack, comfortably pouring out more coffee. “Is not identity something you are born with?”
“The identity I am thinking of is something that hovers between a man and the rest of the world: a midpoint between his view of himself and theirs of him—for each of course affects the other continually. A reciprocal fluxion, sir. There is nothing absolute about this identity of mine.  “And I dare say they call me Beelzebub. But that don’t make me Beelzebub.”
“Does it not?”
—Patrick O’Brian, Master and Commander
PART I: The Murderer and the Journalist
Chapter 1: The Strangers’ Grave: A Catechism
The pistol fired. A woman screamed. The end of his story began.
Was attention paid? By whom? Begin again.
It was September 4, 1835, just before midnight on a Friday in New York, and a night watchman named Richard Hockman was patrolling the seam between two of Manhattan’s rougher neighborhoods.
Who was Richard Hockman? Why was he a night watchman?
He wanted a job. These were the years before New York had a regular police force. Hockman and his fellow night watchmen worked days as stevedores, teamsters, and mechanics. Nights, when Hockman was done unloading ships or driving wagons creaking with beer, he reported to a Watch House. He donned the only piece of his uniform that he didn’t own: a modified fireman’s helmet, varnished twice a year until it was hard as iron. It earned watchmen the nickname ‘leatherheads.’ And at nine each night, he went to work again, patrolling the streets on two-hour shifts with only a rattle and a thirty-three-inch truncheon to keep him safe.
Where was he that night?
Stationed on Monroe Street, in the Seventh Ward, three blocks northwest of the East River, Manhattan’s conduit to the waxing, waning Atlantic World. Three blocks from the cutters, sloops and schooners from Europe, Africa, and the Indies that clung to its docks. Their bowsprits stretched across the footway, almost grazing the city’s windows, and their gangways spilled their guts along the city’s streets.
What did they contain?
Money and men, sometimes interchangeable. Slavery had ended in New York State eight years before. But elsewhere—in the southern United States, Brazil, Cuba—the institution was very much alive. The sugar, cotton, and coffee that slaves produced passed through the fingers of New York financiers like beads on a rosary, or links on a chain. They were sold and traded for silk and metal from England and China, and good American coin. By day, the ships exhaled the tanned and bleached sailors that hauled their loads, and at night the city inhaled, taking their earnings in exchange for food, bed, and, “Oysters in every style.”
And did they drink?
They drank, yes. A block away from Hockman, on Water Street, beneath walls tattooed with colored prints of ships and flags, they drank. Beneath American eagles, Queen Victoria, and George Washington, they drank. Beneath candles that shone through colored glass, they belted out the ballads of “William and his Black Eyed Susan” and “Paul Jones the Pirate.” And then they drank some more. On a Friday it might have been hard to hear anything else.
And what about the women, walking Gotham by gaslight?
A pistol fired.
A woman screamed ‘Watch!’
Another cried ‘Murder!’
And Hockman, the night watchman, began to run. Where?
Towards the commotion: a boarding house at No. 6 Monroe Street.
Who was waiting at the gate?
Two women. The first was Mrs. Harriet Shoults. She rented two rooms in the boarding house above.
Who was she? How did Harriet Shoults make money?
Like many poor women in New York, Mrs. Harriet Shoults made money as many ways as she could. She washed clothes. She rented out one of her rooms to boarders, like the other woman waiting at the gate.
Who was she? What did she do for a living?
Her name was Eliza Seymour; the newspapers didn’t say.
But what else was the Seventh Ward known for?
Prostitution, a growth industry. This was where it began in New York, and the surge in single men, sailors, and traveling businessmen had created a staggering demand. By 1820 there were more than two hundred brothels citywide, and nearby Water Street teemed with opportunity. Streetwalkers called out to sailors and longshoremen fresh from the docks, beckoning them inside. Thirty prostitutes at a time haunted the ferry houses, like the one around the block from Monroe, where Catherine Street ended. They caught young clerks leaving the office, on their way home to Brooklyn.
Who were these “girls on the town”? And where did they live?
Here, there. In brothels, and in boarding houses, like that of Mrs. Shoults. They were good tenants: hungry, entrepreneurial, uncovering themselves in doorways to stay warm. They were white, black, often poor but sometimes wealthy, running their own businesses, making their own money. Many were from the ranks of immigrants and rural arrivals that quintupled the city’s size from 1790 to 1830. In a city of 270,000, social reformers claimed that prostitutes numbered as many as 10,000. The real number was probably closer to 3,000. But more when times were bad.
Were times bad that September?
It depends on who you were. If you were a merchant, then business was booming. But if you were a woman, if you were foreign, if you were poor, then high rents and rampant inflation made life wretched.
Who else was waiting at the gate?
A man, smoking a musty cigar.
Who was he?
His name, the watchman learned, was Richard C. Jackson, and he was a sailor.
He was one of Mrs. Shoults’ other boarders.
He spoke with a foreign accent.
And according to the women, he had just shot a man.
Was New York that violent? Was it more violent than it used to be?
Yes.
It was bigger, richer, but also tighter, poorer, more diverse. In places where those worlds rubbed together, like prostitution—whites sleeping with blacks, the wealthy with the poor—pride, prejudice and resentment boiled over into violence. New York would only see seven murders go to trial in 1835, but the suspiciously dead turned up regularly, along with the victims of other violent crimes. The 1830s was the era of brothel riots, and for four nights in 1834 white mobs had attacked blacks and the abolitionists who demanded the end of southern slavery. White Bowery B’Hoys and “brothel bullies” ganged together and went on sprees, roaming from saloon to saloon, and brothel to brothel, threatening wealthier prostitutes with rape and blacks with worse. In 1836, the following year, the country would be horrified by the brutal murder of Helen Jewett, a prostitute from Maine.
Was Jackson a brothel bully?
He was a sailor, amongst other things.
Did he try to escape?
He did not, though all agreed that Jackson could have made a run for it if he had wanted to. He was very calm instead; mild and composed, even. He was not addled by liquor, the witnesses claimed. When Hockman took charge of him, he didn’t resist.
What did Hockman do next?
He left Jackson in the care of a fellow watchman, and then walked down the alley, into the darkness. He climbed the rickety stairs to Shoult’s quarters. He opened the door.
What did he find?
A room, about fourteen feet square, bathed in candlelight. He saw a bed, a bedstead, and a body laid out upon the floor.
Whose was the body?
His name was John Roberts, “Little Jack” to his friends. He had been born in Prussia thirty years before. He was also a sailor. His ship had arrived in New York that very morning.
Was he alive?
Hockman got closer, and saw that a small stream of blood, about three feet long and growing, ran across the floorboards from Robert’s head. The night watchman “took him by the hand to see if there was any life in him.” There was not.
What else did Hockman observe?
That the bed had been sat on, but was otherwise unrumpled; that there was no liquor, and no glasses.
Was there anything Hockman missed?
A chair, where the murderer once sat.
What did Hockman do next?
He went downstairs and looked closer at Jackson.
He was not a bad looking man, the newspapers later reported, but an intense one. About five feet nine inches tall, he had
a slight but apparently agile frame, and a swarthy weather-beaten countenance. His cheek bones were broad and high, and his eyebrows were dark and heavy; but the expression of his eyes were rather humorous than ferocious, not withstanding the shade of care which bedimmed them.
He was only thirty-five, but looked forty. There was a quiet, melancholy air about him, and a scar, on his forehead, two or three inches long.
Was the murderer still armed?
He was. Hockman asked Jackson what he had done with the gun. Jackson reached inside his jacket, a short blue frock, and from an inside pocket pulled out a pistol with a brass barrel.
“Here it is,” he told Hockman.
Was that all?
No. He also had a knife, which Hockman took as well.
Did the watchman and the murderer wait around for the crowd to develop?
They did not. Hockman took Jackson to the Watch House on Chatham Square, three blocks to the northeast, at the edge of Five Points.
And what was Five Points?
It had a reputation for being “the most notorious slum in the Western Hemisphere.” It had more brothels than any other neighborhood, and more brothel bullies. Pigs rooted for cabbage stalks in a menacing labyrinth of streets that made outsiders uneasy. It was far from Broadway’s cobblestones, coaches, phaetons, tilburies, and carriages.
But for many, Five Points was home. The hard-up working class, white and black alike, lived here and made do with what they could. In the bedroom, and on the street, this was the most racially integrated neighborhood in New York. Buildings that once housed single families became tenements and boarding houses, where multi-generational families and workers dossed together in single beds, or mounds of rags, straw and shavings. Even in the darkest rooms, wrote Charles Dickens after a visit to New York a few years later, “[t]hey have a charcoal fire within; there is a smell of singeing clothes, or flesh, so close they gather round the brazier…”
So close that the buildings often burned, leaving charred husks exposed to the moonlight.
Did black fiddlers and tambourine players beat out a tune as dancers twirled in dark basements?
So wrote the novelist, when he toured them in the company of the watch.
Did Jackson resist, as Hockman marched him onto that supposed Golgotha?
He did not.
How long was the walk to the Watch House?
Three minutes. From Monroe, they turned right on Catherine. They walked along the sidewalk, or perhaps in the center of the road. They passed a dry goods store named Lord and Taylor.
Did Jackson, the sailor, stop and gaze through the plate glass window at the women’s clothes? Did frocks, shawls and memory catch him by surprise?
By night, the shop lay dark.
Did Hockman and Jackson talk as they walked? Did they converge from parallel pasts?
Hockman asked Jackson why he killed Roberts.
Did Jackson respond?
“He has deprived me of my comfort,” Jackson replied, in his light foreign accent. “And I have taken his life.”
What comfort had Roberts taken? What comfort had Jackson lost?
Dickens visited New York’s cemetery. “The saddest Tomb I saw there,” he wrote, “was ‘The Strangers’ Grave. Dedicated to the different hotels in this city.’”
Jackson smoked his cigar all the way to the watch house. When they arrived, Hockman handed the sailor’s pistol to the foreman, and Jackson went into a cell, alone. He was to wait there until six o’clock that morning, when he would be taken back to Mrs. Shoults’s for the coroner’s inquest.
Did the sailor say anything once in the Watch House? Did he show remorse?
 Another watchman told Jackson he’d hang for it. Jackson did not reply.
Who was Roberts? What was his relationship to the landlady, Mrs. Harriet Shoults?
He was a sailor.
She did his laundry.
He visited her when he was home from sea.
Was that all?
When the watchman took Jackson away, Shoults ran to No. 161 Madison Street, to find Roberts’s friend, James J. Richardson. She banged on the door, waking him up. “For God’s sake, James,” she said, “come around to my house, for there is a murder there.” The friend followed her back to No. 6 Monroe. “There was no man there but the dead man,” he later told the court.
Where was Mr. Shoults?
He lived at No. 50 Oliver Street, a two-minute walk from Mrs. Shoults’s boarding house, on the way to Five Points.
They didn’t live together?
“The fluid structure of prostitution even enabled working-class couples to enter and leave the trade periodically,” writes the historian Eric Gilfoyle: “skilled artisans, saloonkeepers and families slipped in and out of the underground economy. Commercial sex was a means to a supplementary income and a quick profit.”
But what does that mean? Was Harriett Shoults a prostitute? Was Harriet Shoults a madam?
She was a landlady. But the line between a boardinghouse and a brothel was … blurry. Brothels posed as boardinghouses, and boardinghouses sheltered prostitutes. And then there were the panel houses.
And what was a panel house?
A house where prostitutes lured a man and robbed him, often with the help of a second man.
So what was Jackson to Shoults? Why did Jackson kill Roberts?
“Roberts had taken away his comfort,” explained another newspaper, “and he had now taken him out of the way.”
Roberts came ashore that morning with pockets full of pay. Where did his money go? Who profited?
As a member of the watch, Richard Hockman, received one dollar and fifty cents per night. For taking Jackson into custody, he would have made another at least another twelve and a half cents. For getting Jackson to prison, he made yet another twelve and a half cents. Hockman faced dawn with an extra dollar and seventy-five cents jingling in his pocket.
Roberts’s money went unmentioned.
And how much did working women make?
Perhaps no more than thirty-seven and a half cents per day. Two dollars a trick, if they were a prostitute. And a virgin could make much more.
What comfort had he taken? What comfort had she lost?
Harriet Shoults did not sleep that night. The police made sure she stayed put for the coroner’s inquest the next day.
Did Jackson sleep?
No: he tried to kill himself.
The watchman Charles Foster checked in on Jackson three times over the course of the evening. At one point, he left Jackson for three quarters of an hour. Foster tried to enter the cell when he returned, but something stopped the door from opening. Foster pushed his hand in and felt fabric—a handkerchief tied taut to the bars. He moved his hand down and felt Jackson’s body, hanging from the cell door.
Foster cut Jackson down. The mariner’s face was black and breathless. He was insensible at first. But then he breathed.
Foster carried Jackson upstairs. He threw water in the sailor’s face. Jackson recovered in about twenty minutes, and the watchman returned him to his cell.

Who was Richard Jackson?
He was a sailor.
He spoke with a foreign accent.
And in truth, his name wasn’t Richard Jackson.
TO BE CONTINUED IN OUR NEXT ISSUE.
The author would like to thank James Sidbury and James Sweet for comments and encouragement on earlier versions of this piece. Their contributions will be even more apparent in forthcoming chapters. The author would like to thank Jean-Pierre Hufnagel for his micro-film surfing.


--- title: EMCC - East Metro Collaborative Competition layout: default bodyClass: page-home ---
EMCC is open to the public & admission is FREE…
Spectators are welcome to attend and enjoy the action!
EMCC will return to a normal competition on Sept 24th 2022. Please return to this site in a few days when more information is available.
EMCC 2022 will take place on 09/24/2022 in East Ridge High School's gymnasium, Woodbury, MN. See FAQs page for more details.
If you have any questions or comments: please send a note to<EMAIL_ADDRESS>At this time our school district has no Covid 19 restrictions in place. Please refer back to this page to see if things changeAttendees should follow common sense CDC guidlines, the most important being: If you have any symptoms, please stay home so you don't infect others!
This event will store and livestream audio, video and still images that may include anyone attending the event. By entering this event you agree to this.


I built the wall, I put letters and colors on
I made a hole, I peeked through and like what I saw
So, I broke it down and on some other ground
From the start, all over again,
as a new chalange, on demand...
I built the wall, I put letters and colors on
I made a hole, I peeked through and like what I saw
So, I broke it down and on some other ground
From the start, all over again,
as a new chalange, on demand...
If you want to break and build walls with me check out my portfolio and skills


Available Courses, Add Course, Delete Course , Update Course
Available Faculty, Add New Faculty, Remove Faculty, Update Faculty Info
Assign Suitable Course to faculty


Gujarat High Court Case Information System Print CA/11325/2010 1/ 4 ORDER IN THE HIGH COURT OF GUJARAT AT AHMEDABAD CIVIL APPLICATION - FOR VACATING INTERIM RELIEF No. 11325 of 2010 In SPECIAL CIVIL APPLICATION No. 6233 of 2010 ================================================= FILATEX INDIA LIMITED - Petitioner(s) Versus VALSAD JILLA PARIYAVARAM TRUST THROUGH PRESIDENT & 13 - Respondent(s) ================================================= Appearance : MR MJ THAKORE, SR. ADVOCATE with MR RAMNANDAN SINGH for Petitioner(s) : 1, MR MUKESH A PATEL for Respondent(s) : 1 - 3. MR PK JANI, GOVERNMENT PLEADER for Respondent(s) : 4 - 9,11 - 12. MR SUNIL L MEHTA for Respondent(s) : 10, MR SN SINHA for Respondent(s) : 13, None for Respondent(s) : 14, ================================================= CORAM : HONOURABLE THE CHIEF JUSTICE MR. S.J. MUKHOPADHAYA and HONOURABLE MR.JUSTICE ANANT S. DAVE Date : 24/09/2010 ORAL ORDER
(Per : HONOURABLE THE CHIEF JUSTICE MR. S.J. MUKHOPADHAYA) The writ petition in public interest has been filed by the petitioner for a direction to the respondent authorities to stop the activities of the 12th respondent of establishing the industrial unit at village Nani Tambadi, District Valsad. Apart from the above plea, it is also pleaded that the small agriculturists in the area have spent huge amount for development of their land. Now due to demolition of the sub-canals while levelling the land by the 12th respondent, the irrigation facilities to their fields will be disturbed. It is also alleged that no prior permission has been taken from the competent authority.
2. This Court while issued notice on the respondents on 2.7.2010, prohibited the 12th respondent from making any further construction on the land purchased by it. The said interim order was allowed to continue subject to the order that could have been passed in the petition for vacating stay preferred by the 12th respondent.
3. The learned counsel appearing on behalf of the 12th respondent pressed the petition for vacating the interim order of stay.
4. We have heard the parties in detail.
5. It appears that the Gujarat Pollution Control Board has granted conditional permission under the Water Act, 1974 and the Air Act, 1981 wherein the following conditions have been laid down:-
1. This order is subject to the outcome of the final order of Honourable High Court in SCA No. 6233 of 2010.
2. You can establish industrial plant only to manufacture TEXTURIZED YARN.
3. You must obtain all necessary approvals from various government departments before to start construction.
4. You must obtain N.A. permission from competent before to start construction activities.
5. You will have to obtain the environmental clearance from the competent authority for the products which required prior E.C. before to start construction activities for that product.
6. You have to take all necessary precautions to control noise pollution. You will not carry out any activity which may crease pollution related problem in surrounding area.
6. Per contra, the learned senior counsel appearing on behalf of the 12th respondent submits that the N.A. permission as has been ordered to obtain is not required to be obtained in the present case. Further, according to him, the environmental clearance from the competent authority is also not required as the products which the 12th respondent intends to make do not require prior environmental clearance before starting up the production activities.
7. The Collector, Valsad in his affidavit has given details of land being Survey Nos. 102, 103, 104/1, 104/2, 105, 106 and 121 of village Nani Tambadi, Taluka Pardi, District Valsad. It is stated that the 12th respondent intimated that they have started bona fide industrial use as per Section 63AA of the Gujarat Tenancy and Agricultural Lands Act, 1948 and they are required to intimate within 30 days as per the Government of Gujarat Ordinance No. 3 of 1996 dated 26.6.1996. Now the matter has been intimated to the Collector by letter dated 25.2.2010. As per Section 65B of the Bombay Land Revenue Code and Government Ordinance No. 2 of 1996 dated 26.6.1996, the 12th respondent occupant required to use the land for bona fide industrial use is not required to take prior permission from the Collector. However, the 12th respondent is under an obligation to intimate within 30 days and the post facto N.A permission is required to be obtained after scrutinizing the necessary papers. After the intimation was given by the 12th respondent on 25.4.2010, a large number of objections appears to have been received from the villagers. Therefore, no post facto N.A. Permission is granted till date.
8. Taking into consideration the aforesaid facts, while we are not inclined to vacate the interim order of stay for the present, allow the 12th respondent to move before the competent authority to obtain necessary permission as per the conditions imposed by the Gujarat Pollution Control Board. If such permission is sought for from the competent authority, including the permission as already sought for from the Collector, Valsad, the authorities will consider and decide the same in accordance with law during pendency of the case and any such decision shall be subject to the decision in this case. It is expected that the Collector, Valsad will decide the matter on the application of the 12th respondent taking into consideration the objections raised by the villagers on an early date, preferably within one month.
This Civil Application stands disposed of.
[S.J.
MUKHOPADHAYA, CJ.] [ANANT S. DAVE, J.] Sundar/* Top


How do I... Read and write to the file system?
Need to interact with the local file system? It's easy with Elixir, just use the File.* module.
If you are trying to download a file, the best way to go is to stream it from a remote URL to your file system directly, which can be quicker and avoids filling up memory on your server. The simplest way to do so is with this Erlang snippet:
# Note, this is Erlang, so it looks odd, but it runs fine, and it is built in
# Just note, in Erlang, you need to use single quoted strings
# Also you need these two lines
:inets.start()
:ssl.start()
# This path is relative to the current working directory (see File.cwd/0)
save_path = '/mypic.jpg'
image_url = 'http://exmple.com/img/pic1.jpg'
:httpc.request(
:get,
{image_url, []},
[],
body_format: :binary,
stream: save_path
)


|
ep_fg_model_select()
|
Select the columns needed for EP predictions |
|
get_preds_ep()
|
Select the columns needed for EP predictions |
|
create_epa()
|
Create EPA
Adds Expected Points calculations to Play-by-Play data.frame |
|
epa_fg_probs()
|
Performs Field Goal adjustments for Expected Points model calculations |
|
create_wpa_naive()
|
Add Win Probability Added (WPA) calculations to Play-by-Play DataFrame
This is only for D1 football |
|
create_wpa_betting()
|
Add Win Probability Added (WPA) calculations to Play-by-Play DataFrame (Betting)
This is only for D1 football |
|
add_betting_cols()
|
Add Betting columns
This is only for DI-FBS football |
|
clean_drive_info()
|
Clean Drive Information
Cleans CFB (D-I) Drive-By-Drive Data to create `pts_drive` column |
|
penalty_detection()
|
Penalty Detection
Adds penalty columns to Play-by-Play data pulled from the API |
|
add_play_counts()
|
Adds play counts to Play-by-Play data
Adds play counts to Play-by-Play data pulled from the API's raw game data |
|
clean_pbp_dat()
|
Clean Play-by-Play data
Cleans Play-by-Play data pulled from the API's raw game data |
|
clean_drive_dat()
|
Create new Drive results and id data
Cleans Play-by-Play data pulled from the API's raw game data |
|
prep_epa_df_after()
|
Creates the post-play inputs for the Expected Points model to predict on for each game |
|
ep_model_select()
|
Select the columns needed for EP predictions |
|
ep_model_select_check()
|
Select the columns needed for EP predictions |
|
wp_model_select()
|
Select the columns needed for WP predictions |
|
wp_model_select_check()
|
Select the columns needed for WP predictions |
|
penalty_detection_select()
|
Select the columns needed for penalty_detection() |
|
add_play_counts_select()
|
Select the columns needed for add_play_counts() |
|
clean_pbp_dat_select()
|
Select the columns needed for clean_pbp_dat() |
|
clean_drive_dat_select()
|
Select the columns needed for clean_drive_dat() |
|
add_player_cols_select()
|
Select the columns needed for add_player_cols() |
|
add_yardage_select()
|
Select the columns needed for add_yardage() |
|
prep_epa_df_after_select()
|
Select the columns needed for prep_epa_df_after() |
|
prep_df_pbp_overview()
|
prep_df_pbp_overview |
|
check_internet()
|
Utilities and Helpers for package |


A common source of frustration among budding developers is acquiring the experience necessary to move past the early stages of programming and computer science. Year of Programming is an active community of dedicated participants that encourage each other to acquire daily experience in problem solving, programming and computer science through collaboration. Every year means new challenges and new faces - welcome to 2017!
We will periodically release a new programming challenge through our GitHub Repository. As a participant, you will solve this challenge with the programming language of your choice. Additionally, we ask that you document your thought process, explain how to compile your code, and describe how to use your program.
When finished, you will submit your code for review and your peers will review your code and give you feedback. Once enough people have reviewed and approved of your solution, we will merge your code onto the repository and the solution will be stored there for that challenge.
Most of our communication is done through our Slack channel. You can discuss anything from the challenges to developing technologies to career advancement and everything in between. It is highly recommended that you join the Slack channel in order to properly participate.
As programmers and developers, we are all constantly seeking improvement. This process is designed to develop your problem solving abilities and to promote a higher standard for beginning and intermediate programmers. By the end of the year, you will be able to:
Additionally, our Slack channel is an invaluable resource for tools, insight, and code review from professional programmers and intelligent students from around the world. We provide the means to open source your training as a developing programmer.
Each challenge will be posted in its own folder, in numbered order. Each challenge folder will have a Challenge.md file describing the challenge, and may have some example code or test cases provided. Do your very best to avoid help for as long as possible.
If you have a question, first try to ask it to yourself out loud - it's a proven trick!
To submit your solution, open a pull request on the main repository. We'll make sure that merging won't cause any problems, and go from there.
When submitting a pull request please use the following format for your title: [Language] Challenge # (UnderReview)
For a more comprehensive guide on how to use GitHub for these challenges, visit this page


“Manujassa pamattacārino,
Taṇhā vaḍḍhati māluvā viya;
So plavatī hurā huraṁ,
Phalamicchaṁva vanasmi vānaro.
When a person lives heedlessly,
craving grows in them like a parasitic creeper.

Yaṁ esā sahate jammī,
taṇhā loke visattikā;
Sokā tassa pavaḍḍhanti,
abhivaṭṭhaṁva bīraṇaṁ.
Whoever is beaten by this wretched craving,
this attachment to the world,
their sorrow grows,
like grass in the rain.
Yo cetaṁ sahate jammiṁ,
taṇhaṁ loke duraccayaṁ;
Sokā tamhā papatanti,
udabindūva pokkharā.
But whoever prevails over this wretched craving,
so hard to get over in the world,
their sorrows fall from them,
like a drop from a lotus-leaf.
Taṁ vo vadāmi bhaddaṁ vo,
yāvantettha samāgatā;
Taṇhāya mūlaṁ khaṇatha,
usīratthova bīraṇaṁ;
Mā vo naḷaṁva sotova,
māro bhañji punappunaṁ.

Karotha buddhavacanaṁ,
khaṇo vo mā upaccagā;
Khaṇātītā hi socanti,
nirayamhi samappitā.
Act on the Buddha’s words,
don’t let the moment pass you by.
For if you miss your moment
you’ll grieve when you’re sent to hell.
Pamādo rajo pamādo,
pamādānupatito rajo;
Appamādena vijjāya,
abbahe sallamattano”ti.
… Mālukyaputto thero ….
Negligence is a toxin;
negligence is included as a toxin.
Through diligence and knowledge,
pluck out the dart from yourself.


--- layout: post title: "[UPDATE] A Quick One" date: 2020-03-21 01:45:00 -0400 background: '' --- Hello hello! We're here to let you know everything is on track and looking good. A redesign of the GUI was required as the previous design could not process large files, but other than that everything is on track for the symposium! We recently had a design and filming night and were able to get all the small design fixes complete and the LCD wired up. All that's left is calibration and test prints :D
Yours Truly,
Formagine