sadat2307/MSciNLI huggingface dataset:
Domain: Software and its engineering
Sentence 1: However, that would be a tedious and error prone process.
Sentence 2: for parsers that use Parsec s LanguageDef abstraction, adding the check to the lexeme combinator would handle many cases, but even then, many primitive operators such as char, digit, and satisfy do not use lexeme so we would have to be careful to also add checks to such primitives.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: With at least 2f +1 execution replicas in other BFT-SMR systems, a recovering replica is guaranteed to get at least f +1 valid and matching checkpoint messages from other execution replicas, allowing checkpoint creation and valida­tion to be done exclusively within the execution cluster [Yin 2003].
Sentence 2: zZ runs only f +1 execution replicas in the normal case, and thus a new replica may not be able to tell which of the checkpoints it is provided are correct.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: X10 supports generics in whichthe type parameters are speci.ed using [] (line 1).
Sentence 2: in X10,type parameters are not erased during the compilation, thereforeprogram can introspect the information during execution (line 16).X10 does not support dynamic class loading in favor ofoptimization opportunity by wholeprogram analysis.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: It is clear that considering recommendations from various usability research studies on navigation model are all very important and should be implemented for designing well­organized sites and it may also help improving the adaptive display methods that can be more effective at directing people to the right place by matching user expectations.
Sentence 2: mobile computing is evolving rapidly and due to variations in mobile devices screen size, its' features and other related issues, these differences may lead to different rules, such as when the web site is adapted the preferred and optimal page length will also depend on the page's content [8] and what is recommended today may not fulfill the requirements in future changing environment.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The probability of correct classi.cation as FP is also small because both FP and NFP corpuses contain the same .x-on-.x lines.
Sentence 2: if the module is misclassi.ed as NFP, the module s FP lines, which are similar to the .x-on-.x lines, are stored in the FP corpus with the TOE procedure.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Using implicit con­currency allows kernel code to be written without explicit attention to timing issues; for example, there is no need to bound the execu­tion time of a pure sub-computation because an interrupt will even­tually cause a thread switch if necessary.
Sentence 2: under this ap­proach, many of the state-based assertions given in this section are not really true because another thread may execute in between two apparently consecutive operations.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: We are very interested in determining whether uniqueness types are subsumed by, or can be integrated with, related resource­conscious logics such as Bunched Implications [19] or Sch¨ opp and Stark s dependent type theory for names and binding [24].
Sentence 2: this technique for encoding .nite partial maps only works for functions whose domain is a set of names.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Asblockswithrecentlyupdatedsectorsresideinthe PMA, the PMA can be regarded as a cache with hit rate r. Now, with probability r, a sector write can be done with cost CPW .
Sentence 2: with probability of (1 - r), a sector write pays a cost of CDefusion + CF usion + CPW because it incurs a Defusion to evict the LRU block from the PMA, a Fusion to migrate the newly referenced block to the PMA, and a write of the requested sector to the PMA.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: As done in [6], this allows us to consider interleavings at the level of collection operations, without considering interleav­ings of their internal operations.
Sentence 2: the key insight that we use is that before and after each collection operation op1 executed by the MUT, the environment chooses a col­lection operation op2 to execute that does not commute with  1 V compute(K k) { 2 V val = m.get(k); 3 if (val == null) { 4 val = calculateVal(k); 5 m.putIfAbsent(k, val); 6} 7 return m.get(k); 8}  (a) (b) Figure 3.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Case 1 2 3 4 (a, b, c) (2, 0, 3) (5, 4, 8) (2, 6, 2) (2, 3, 7) L-k P P F F L-1 (a, 2) (a, 5) (a, 2) (a, 2)    L-5 (c, 7) (c, 18) (c, 6) (c, 11) L-8 (a, 2)(b, 9) (a, 5)(b, 4) (a, 2)(b, 15) (a, 2)(b, 12) Table 3.
Sentence 2: theprogramstatesofbranchingstatementsinFigure1  2.2 Fault Localization Takingafullcoverageofallprogramstatesrequiresaconsiderableamountoftimeandspace.onlyafewofthemarerelatedtothefaultystatementwhiletherestofthemarecompletelyirrel­evant.Take(c, 2, L-2) and(c, 7, L-4) inTable2asanexample.Bothstateshaveafailurerateof1.0simplybecausetheyonlyap­pearinafailedcase.ByexaminingthecodeshowninFigure1,welearnthatbothstatesareirrelevanttothefault.Consideringthatitisanexpensiveoperationtoanalyzealargenumberofrecords,weshouldavoidrecordingtheseirrelevantprogramstatestoimproveitsef.ciency.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: An Externally Replicated Experiment to Evaluate Software Testing Methods Sheikh Umar Farooq Department of Computer Sciences University of Kashmir, India suf.cs@uok.edu.in ABSTRACT Context: Many empirical studies have been carried out to evaluate software testing methods in the past decades.
Sentence 2: we are still not able to generalize the results, as most studies are not complete and differ significantly from one another.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Admittedly, the community that is interested in building data collection tools seems to be converging to an implicit paradigm of constituent components for the tools, as indi­cated by an agreement on the need for client-server com­ponents and con.guration interfaces[13][8].
Sentence 2: it has only been roughly outlined and has not yet been made explicit in more speci.c terms.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Diverse types of approaches have been proposed to monitor requirements at runtime [9], e.g., per­formance and event monitoring techniques [14, 4].
Sentence 2: the characteristics of SoS lead to additional challenges: re­quirements may exist at di.erent levels e.g., at component level, system level, or SoS level and may be overlapping or con.icting.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In the case of scale up, if the size of a data request queue associated with a particular processor node re­mains close to zero consistently, the adaptation mechanism considers this as an indicator of good performance, implying that there are active DRPPs which probably are not neces­sary and have to be deactivated.
Sentence 2: if the queue size increases consistently, scale up tries to increase performance by activating new DRPPs.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: ProgramhekerssuhasESC­Java[9]allowannotations thatspeifypropertiesoffeldsthatareverifedaspartof thehekingproess.Thesepropertiesinludeaspeifa­tionthatafeldisnon­nullorthatamethodreturnsanew, unaliasedobjet.Ourompilerattemptstodisoverthese propertiesautomatially,ratherthanusingprogrammeran­notations.
Sentence 2: dolbyandChien[12]desribeanobjetinliningopti­mizationforC++programs.Theiranalysisusesafully ontext­sensitiveinterproeduralframeworkandthusallows objetinlininginspeifasesonafeldthatannotbein­linedingeneral.Inpartiular,theydonotrequirethat thefeldbeinitializedwithanewobjetintheonstru­tor.theiranalysistimesaremeasuredinminutes, whereasouranalysisisalwaysonlyasmallnumberofse­onds.Also,weallowanobjettobeinlined(withaheader), evenifareferenetotheobjetesapestheloalontext.A largeamountofrelatedworkwithrespettoobjetinlining (orunboxing)alsoexistsforfuntionallanguages[14,16,19], asdesribedin[12].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Distributed AOP defines many new concepts like remote pointcuts [1], which are similar to traditional remote method calls, since execution is implied on a remote host; com­ponent-aspects [2,8], which introduces some features from com­ponent models, and aspect group notions [3], thus establishing a context where aspects can be deployed in a set of hosts.
Sentence 2: we can find three major drawbacks in these current distributed AOP works.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Performance comparison in uncoordinated crwodsourcing As shown in the previous figure, the uncoordinated search approach (also used by Google s OpenSpot) fails to help smart parkers do a better job than ordinary drivers in the search of parking spots regardless of how many drivers participate.
Sentence 2: the coordinated strategy we proposed in section 3 guides smart parkers more wisely.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Typically, an architecture-independent pro-gram representation (e.g., bytecodes for the Java language) is shipped to the execution site and interpreted by a vir-tual machine.
Sentence 2: to overcome the performance lim- itations interpretation usually imposes, these systems now employ just-in-time compilation [25, 2, 19, 11].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In general, when joining two quanti.ers .U(F1 .e)and .U(F2 .e)from different quanti.ed domain elements, a safe answer is .U(F1 .F2 .e)(meaning it over­approximates the .of the two inputs).
Sentence 2: doing such a sim­ple conjunction of guards will almost always lead to imprecision.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In the past most of the techniques used were manual, such as drawings, physi­cal models, or interactive displays, and were used in face-to­face situations such as workshops and exhibitions.
Sentence 2: recently, academics and practitioners have begun to explore applications of digital media to participatory design, looking at interactive websites and geographic information systems (GIS) in particular [19, 4].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Fault pattern analysis results.
Sentence 2: suspect Chip 1 Chip 2 Chips 3 5 defects #FP # Cell #FP # Cell #FP # Cell FP1 2 6 3072 10 5120 FP2 2 8 4096 16 8192 FP3 1  45 23040 FP4 2 25 12019 15 7434 FP5 1  5 5120 FP6 1  2 2048 FP7 2    1 384 FP10 6 2 2 18 18 FP11 6 3 3 13 13 FP12 3 175 175 896 896 FP13 1 90 180 FP14 1 114 228 FP15 1 7 14 4 8 FP16 1 86 172 23 46 FP17 1 68 136 30 60 FP18 1 7 14 4 8 FP19 1 14 28 2 4 FP20 1 17 34 1 2 FP21 1 83 166 FP22 1 73 146 Unknown  1352  4706 Total  21848 56715 384 Chips 1 and 2 had a large amount of failed columns.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: To achieve that one needs to specify some (possibly arbitrary) static tie-breaking rules.
Sentence 2: there exist instances for which no Nash equi­ 2Price of stability is de.ned as the ratio between the social value of the best Nash equilibrium and the social optimal so­lution, while price of anarchy is de.ned as the ratio between the social value of the worst Nash equilibrium and the social optimal solution.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Support for Seamless Linkage betweenLess-Detailed and More-Detailed Representations for Comic Design  Junko Ichino Abstract University of Electro-Communications Through a study of comic design practice, we observed 1-5-1 Chofugaoka that comic designers created three components Chofu, Tokyo 182-8585 JAPAN character-config, plot, and storyboard and used a ichino@is.uec.ac.jp trial-and-error approach with iterative progression from less detailed to more detailed representations during Tomohiro Makita the early stages of design.
Sentence 2: existing comic University of Electro-Communications design tools do not support these tasks very well.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: GCIMS Architecture 4.4 Implementation of Architectural Strategy The integration of all these criteria produces a different perspective on the implementation strategy for clinical information systems, namely, each community has to be responsible for creating and evolving their own CIS.
Sentence 2: to satisfy systems wide access and reuse of ALL data there has to be a unifying coherence that they all participate in.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For example, here are the types of the data type constructor App, and its monadic counterpart (remember that Expr = Q Exp): App :: Exp -> Exp -> Exp app :: Expr -> Expr -> Expr The arguments of app are computations, whereas the arguments of App are data values.
Sentence 2: app is no more than a convenience function, which simply performs the argument computations before building the result: app :: Expr -> Expr -> Expr app x y= do{ a<-x; b<-y; return (App a b)} This convenience is very worth while.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Whilst critical branching nodes determine whether T will be reached in the control .ow structure of the program, other branching nodes may also exist within p that control assignments to variables that are also responsible for determining whether T will be exe­cuted or not.
Sentence 2: it is not possible to know which of these branching nodes should be included for the purposes of computing the .tness function, since P is not known a priori (.nding P is in general undecidable), and neither is the exact sequence of nodes in each p. The path problem exists in the example of Figure 1a where there are four potential paths ending in T .
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Yuji Kyoya and Kunio Noguchi Software Engineering Center Toshiba Corporation Japan (CMMI-SE/SW) has been developed to solve the problem of using multiple CMM models for different areas of application, CMM has been working so well in many organizations that they do not have plans to replace CMM with CMMI immdediately.
Sentence 2: similar to the other SPI models/standards, it does not address the connection between its maturity levels and the business goals of an organization.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: 3.4.2 For New Languages Used in VEE Implementation Dimension is currently written in the programming language C. C is used to implement many VEEs, and these VEEs can use Dimension through the three communication interfaces (i.e., three functions written in C).
Sentence 2: dimension needs some reconfiguration if a VEE is written in a language that cannot directly call functions written in C. For example, the translator in Jikes RVM [1] is written in Java that cannot call C functions directly.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Note, however, that more is required: m in turn invokes a poly- morphic method p, which needs a dictionary of its own.
Sentence 2: we ap- pear at first to have a major problem: the "top-level" invocation of m must construct dictionaries for the complete transitive closure of all polymorphic methods that could ever be called by m. laziness again comes to the rescue: we can simply leave an empty slot in the dictionary for m, filled in dynamically the first time that p> is invoked.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The risk is further reduced by de.ning the concept of idempotent mixins, i.e., mixins that can be repeatedly applied to a class with no adverse effect.
Sentence 2: m-Evolution can still fail if mixin M cannot be applied to V for one of two reasons: If V is a final class, or if the application results in accidental overriding [2] (i.e., a mixin which introduces a new method m() is applied to a class that happens to have a method m() of its own, which the mixin is not meant to override).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If the x86­tier does not perform periodic synchronization and only wakes up once an hour to send and receive updates its average lifetime is found to be 75 hours.
Sentence 2: the cost of this gain in system lifetime is that the expected time to get an update is 1 hours, where p is the probabil­ p ity of a network connection being available.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Other approaches such as split tiling [7, 13], overlapped tiling [11, 13], and diamond tiling [2] have been proposed to address the loss of concurrency when time-tiling stencil computations.
Sentence 2: as explained in the next section, all of the previously proposed approaches have some limitations and drawbacks in the context of GPU computing.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The expenditure of traditional performance test­ing can include but not limited to: 1) salary of engi­neers; 2) cost of purchasing and maintaining infras­tructure; 3) cost of licensing and services.
Sentence 2: the expenditure of cloud-based performance testing can include but not limited to: 1) salary of engineers; 2) cost of cloud pay-as-you-consume resources; 3) cost of licensing and services.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: Note that this constraint does not require any additional implementation e.ort from devel­opers as they would also have to implement the evaluation criteria within some extension point of the EC framework.
Sentence 2: moving the evaluation criteria to classes that de­.ne the optimization problem eliminates the scattering of application-speci.c code within di.erent extension points of the EC framework (as shown in Figure 1C).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In addition, it permits greater .exibility in working around type­checking errors than working with existing code does, and it can be more bene.cial than annotation of existing code, since it pro­vides earlier indication of errors.
Sentence 2: annotation of existing code is more quanti.able, since it is possible to track the time spent annotating and the problems discovered in original code.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If we had not allowed copy folding during the construction of SSA form, the initial union-.nd sets would contain only values that 1 The seeming exception to this is a 4-node parameter, v, whose de.nition is in a block, bv , not necessarily dominating the block, bphi, in which v is used as a parameter.
Sentence 2: the move­ment of the value from the variable to the 4-node actually takes place along the incoming edge to bphi, and this edge is dominated by bv .
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: 6.2 Applicability to Other Domains The solutions presented have a few domain-speci.c components (e.g., the distance metric in the nearest neighbour search and the speci.c error .lters used).
Sentence 2: beyond those components, the various algorithms should be applicable to other problems in the transportation space that involve .nding patterns in a large body of data.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: The optimal software pipelining algorithm, which is given to an­swer Question 2 above, enables us to complete the theoretical treat­ment on time optimal software pipelining.
Sentence 2: the algorithm L3: if cc0 r0 := r1 if cc1 cc0 := (r1==0) store(r2,r1) L2 store(r2,r0) L0 L1 Figure 2: A tree VLIW instruction is of little practical importance; it suffers from excessive overhead in computation time and code expansion.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: CONCLUSION Supercomputers present an interesting point in the design space with respect to dense integration, low per-node power consump­tion, datacenter scale, high bisectional network bandwidth, low net­work latencies, and network capabilities typically found in high­end network infrastructure.
Sentence 2: an esoteric and highly op­timized software stack often restricts their use to the domain of high-performance computing.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: For some benchmarks, this may well hold, though in such cases it isn t clear why the faults from the previous evaluation could not be used.
Sentence 2: since the evidence that coverage is not usefully cor­related with fault detection, when size is held constant, is also weak, adding information on coverage comparisons be­tween suites/techniques as an additional support for a claim of effectiveness could be useful.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: OVERVIEW OF DYNAMINE A great deal of research has been done in the area of checking and enforcing speci.c coding rules, the violation of which leads to well-known types of errors.
Sentence 2: these rules are not very easy to come by: much time and effort has been spent by researchers looking for worthwhile rules to check [27] and some of the best ef­forts in error detection come from people intimately familiar with the application domain [13, 30].
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: There is almost no intersection of sig­ni.cance between all the seven of them, but the possible intersections grow when considering only pairs of project, especially from the point of view of the time period studied.
Sentence 2: while at the moment there is little practical space and time concordance in the project s scope, there are very relevant a.nities in the research subjects, both when considered as conceptual entities (e.g: people, espe­cially scholars, universities, locations...) and on their related properties (e.g: simple biographical information about a per­son, or their curriculum studiorum).
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: If the one-bit error occurs at a parity check bit, and only the circle that contains the parity check bit does not meet the condition of the Even Parity rule, we can easily spot the error without any confusion.
Sentence 2: if the one-bit error occurs at one of the data bits d1, d2 or d3, this will effect the number of 1s in two circles and therefore, we have to take the two circles into consideration for correcting the one-bit error.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In the example, statement l2 de.nes the whole structure a and the statement in l3 de.nes only a.f2, par­tially killing the previous de.nition to a.
Sentence 2: the previ­ous reaching de.nition for ranges of the aggregate variable that were not killed are still valid and a new reaching de.nition only to the range that was reassigned is generated.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In addition, if the data accessed by different threads on the same multiprocessor are aligned and continuous in the device memory, they can be coalesced into a single memory operation to increase memory bandwidth.
Sentence 2: the most frequently reused data are likely to be copied into the shared memory to reduce ac­cess latency, and the banks of the shared memory provide parallel data accesses.
Relationship: contrasting
Domain: Software and its engineering
Sentence 1: In practice, the TinyOS task that resets the array index completes before the ADC interrupt next .res.
Sentence 2: it is worth .nding even latent bugs: TinyOS is designed as a collection of reusable components, and the next application in which the Oscilloscope component is used may have a higher duty cycle, causing the bug to manifest.
Relationship: contrasting