<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02037nam a2200253Ia 4500</leader>
  <controlfield tag="003">MX-MdCICY</controlfield>
  <controlfield tag="005">20260521091535.0</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">CICY</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">B-16738</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">A new strategy for the relative movement of rough surfaces in contact using a boundary element method</subfield>
  </datafield>
  <datafield tag="490" ind1="0" ind2=" ">
    <subfield code="v">European Journal of Computational Mechanics, 25(4), p.309-328, 2016</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Contact mechanics of rough surfaces is becoming increasingly important in understanding the real behaviours of machine elements in contact. Due to the complicated physical, chemical and mechanical phenomena occurring at surfaces, especially in boundary lubrication, a multiphysics numerical model is essential to capture the behaviour. Boundary Element Method is a well-known numerical approach to model such a problem because of several advantages. Firstly, it is far faster than Finite Element Method since only the boundaries of the solids are discretised. In addition, there is no problem of remeshing the contacting bodies due to plastic deformation and wear. Conventional Boundary Element models simulate movement of contacting surfaces by shifting matrices of numbers in one direction. In this new proposed approach, the big matrices of surfaces are cut into small matrices which indicate the part of surfaces that are in contact. The influence matrix is also cut into a smaller square matrix corresponding to the size of surface matrices. This approach enables matrix implications in smaller sizes than the original big surfaces and reduces the computational time.</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">BOUNDARY ELEMENT METHOD</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">CONTACT MECHANICS</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">INFLUENCE MATRIX</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">ROUGHNESS</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Ghanbarzadeh, A.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Wilson, M.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Morina, A.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Neville, A.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://drive.google.com/file/d/1ih2oJbd0vIG6rkJe1-LyF9st04n22xHX/view?usp=drivesdk</subfield>
    <subfield code="z">Para ver el documento ingresa a Google con tu cuenta: @cicy.edu.mx</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">Loc</subfield>
    <subfield code="c">REF1</subfield>
  </datafield>
  <controlfield tag="008">250602s9999    xx |||||s2   |||| ||und|d</controlfield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">26844</subfield>
    <subfield code="d">26844</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">Loc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">F1</subfield>
    <subfield code="a">CICY</subfield>
    <subfield code="b">CICY</subfield>
    <subfield code="c">RE</subfield>
    <subfield code="d">2025-06-25</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">B-16738</subfield>
    <subfield code="r">2025-06-25 16:01:57</subfield>
    <subfield code="w">2025-06-25</subfield>
    <subfield code="y">REF1</subfield>
  </datafield>
</record>
