Merging Sample Clauses

Merging. The PEP may be used and adapted in machine readable form for the purpose of merging it into other program material of the Buyer but, on termination of this Agreement, the PEP shall be removed from the other program material with which it has been merged. The Buyer agrees to reproduce the copyright and other notices as they appear on or within the original media on any copies which the Buyer makes of the PEP.
AutoNDA by SimpleDocs
Merging. In the event two (2) or more runs are merged, the employees on said runs shall bid on the runs affected in order of overall seniority for the right to remain on the merged run or revert to the pool of unbid employees.
Merging. Entity owns or is possessed of or is licensed under such patents, trademarks, trade names and copyrights (including, without limitation, software) as are used in, and are of material importance to, the conduct of its business, all of which are in good standing and uncontested. Schedule 2.18 contains a correct and complete list of all material patents, patent applications filed or to be filed, trademarks, trademark registrations and applications, trade names, copyrights and copyright registrations and applications owned by or registered in the name of Merging Entity. There is no material claim pending or, to the best knowledge of Shareholders, threatened against Merging Entity with respect to any alleged infringement of any patent, trademark, trade name or copyright owned or licensed to anyone other than Merging Entity.
Merging. Entity does not own any real property. Schedule 2.11 also consists of a copy of the depreciation schedules filed as a part of the two prior annual Federal income tax returns of Merging Entity (with deletions of any items disposed of prior to the date of this Agreement), a separate list of each item of depreciable personal property acquired by Merging Entity since the Most Recent Balance Sheet Date and having a cost of $1,000.00 or more, and a separate list of each item of intangible personal property presently owned by Merging Entity. Merging Entity also owns various items of disposable type personal property such as office
Merging. If for two non-terminal nodes u and uj it is true that var(u) = var(uj), then(u) = then(uj) and else(u) = else(uj), then it is possible to remove u and have all edges pointing to it redirected to point to uj. Addi- tionally, if u is a root node, then uj must be made into a root node.
Merging. Meshes We will rst combine M and M b Initiate GenMesh and choose the merge option C genmesh m You are now asked to TYPE infileNAME It makes a di erence which mesh is given rst because that is the one to which the second is subservient Respond m Similarly for the second lename TYPE infileNAME Respond Chapter Model Building with GenMesh m b A brief summary of the two meshes is displayed Now you are asked about how the two meshes are to be attached CONNECTion modes MODEL MODEL continue node to node group to surface intersecting surfaces INPUT mode Note that Model is attached to Model The most basic form of attachment is where essentially the two plates are stitch together node by node The simplest is where any close nodes are automatically connected We will use the second mode for illustrative purposes and you are asked about the attachment nodes INPUT group of nodes release as BC none all interior all The group referred to is the group of boundary nodes at the bottom of the mesh le When two meshes are joined what were formerly boundaries now could become interior regions We therefore may wish to release them and not consider them as boundaries or special collections of nodes anymore Since boundary nodal groups usually overlay at a common node Options and allow distinguishing between the two situations The sequence of attaching is counter clockwise for the rst mesh and clockwise for the second Before getting to this stage it is good practice to use PlotMesh to explore the generic meshes In particular that program can determine the boundary nodes The appropriate information is The attaching is a recurring menu Since we do not want to attach any more segments then to quit type Use PlotMesh to look at this mesh and note the boundary nodes We now wish to merge this new mesh with M b The procedure is the same as what was just done To be di erent we will show the use of the third mode of attachment C genmesh MAIN m m m b
Merging. The actual sharing of hardware resources is implemented as a merging of nodes in the dataflow graph. In order to merge two nodes the inputs to the merged node have to be multiplexed so that either the inputs to the first node or the inputs to the second node are selected. The output of the merged node has to be connected to all nodes that use the result of either node. This process is shown in Figure 6. There are multiple conditions that must be checked before two nodes can be merged. Obviously both nodes need to implement the same operation, but they also have to operate on the same data type. Another condition is that both nodes have to be created in different kernels. To understand why this condition is necessary the properties of the dataflow graph have to be recalled. The actual data flows along the edges through the nodes in a dataflow graph. If the graph gets transformed into hardware, on every cycle new data has to be read from the sources and sent to the sinks in order to maximize throughput and thereby efficiency. If a node is now used twice in the same kernel it has to calculate two different results on the same cycle, which is not possible.
AutoNDA by SimpleDocs
Merging. The objective of the merging step is to pick all artists and albums from all the transformed content provider databases and merge them into one. If we through heuristics find out that two artists from different content providers are, in fact, the same artist, we may merge these artists into one. This way, the artist view in the Spotify client will contain albums from both sources. This could for example be the case when an artist has switched labels during his career, or is released on different labels in different countries.
Merging. Entity does not own any real property. Schedule 2.11 consists of a copy of the depreciation schedules filed as a part of the most recent annual Federal income tax returns of Merging Entity (with deletions of any items disposed of prior to the date of this Agreement). Merging Entity also owns various items of disposable type personal property such as office
Merging. Entity owns or is possessed of or is licensed under such copyrights (including, without limitation, software) as are used in, and are of material importance to, the conduct of its business. Merging Entity owns no patents, patent applications, trademarks, trademark registrations or applications, trade names (other than its corporate name), copyrights or copyright registrations or applications.
Time is Money Join Law Insider Premium to draft better contracts faster.