## You are here

# Comments

### thanks

### Great contribution

### Hi Jinxiong,

*In reply to Modeling Zig-Zag peeling patterns*

Hi Jinxiong,

Your questions are very intersting and challenging. The current input file for adhesion can only simulate the interfacial failure. The co-exist of bulk material failure (e.g., fracture and cavitation) and interfacial failure is very complicated. For this kind problem, new modeling and simulation techniques should be ued. Phase field may be one of the promising methods, but I do not have too much experience on it. The Zig-Zag pattern you referred also needs a fully 3D simulations, which can result in a very large simulation.

Even in interfacial failure, various patterns can exist and be found in a review by Animangsu and Chaudhury (Ghatak, Animangsu, and Manoj K. Chaudhury. "Adhesion-induced instability patterns in thin confined elastic film." *Langmuir* 19, no. 7 (2003): 2621-2631). The cohesive zone model is promising to capture such kinds of instabilities, but may also require a very large scale simulation.

These are all important and challenging questions and definitely call for more studies.

Best,

Teng

### Dear jinxiong,

*In reply to Implementation of Ogden-Roxburgh model*

Dear jinxiong,

Thanks for your interests in our work. The modified Ogden-Roxburgh is already implemented in ABAQUS. The original Ogden-Roxburgh was based on fully icompressible materials, and the modification is to apply the softening to the deviatoric part only for compressible materials. You can find a detailed description in ABAQUS manual

http://abaqusdoc.ucalgary.ca/v6.9/books/usb/default.htm?startat=pt05ch18...

Best,

Teng

### Modeling Zig-Zag peeling patterns

Dear Teng, another question regarding the modeling of adhesion of hydrogels to a rigid substrate. Peeling of soft materials from a bonded rigid substrate may exhibit various patterns. Fracture may occur along the interface of hydrogel and substrate, and this is the interfacial fracture. However, in some cases fracture may occur in the soft materials itself and the peeling results in Zig-Zag fracture pattern. Can your model capture this fracture patterns?

Thanks,

Jinxiong

### Implementation of Ogden-Roxburgh model

Dear Teng, Thank you very much for sharing your ABAQUS files for coupling of Mullins effect and cohesive zone model. These files are very helpful for beginners of learing this fantastic topic and use of ABAQUS to model soft materials. You and Xuanhe made great contribution to the community.

One quick question regarding your EML paper. You mentioned you implement a modified Ogden-Roxburgh model. How did you do that? You directly use the Mullins model provided by ABAQUS or you write a user-subroutine?

Thanks,

Jinxiong

### final version published with some errata corrige

*In reply to Adhesion between a power-law indenter and a thin layer coated on a rigid substrate*

There were some wrong prefactors, if I understand well, which were fixed in final version

See http://casopisi.junis.ni.ac.rs/index.php/FUMechEng/article/view/3588

### Re: Re: stress definition

*In reply to Re: stress definition*

Dear Zhigang,

I agree with most of your points, so I will not touch upon them. I will write only where we seem to differ.

===

In your definition, you say that the domain is the vector space of areas.

However, technically speaking, areas also face exactly the same technical objection as that for the unit normals. ... After all, a unit normal is nothing but only the area vector, as scaled by the reciprocal of its magnitude. Mere scaling doesn't affect the question of whether something is indeed a vector or not.

Area is *not* primarily a vector, but it can be *seen* as a vector, at least for the infinitesimally small parts of arbitrary surfaces, or for planar (orientable) surfaces. Even for such surfaces, the area is not a *primitively* defined vector. It is actually the result-object of taking the cross product of two primitively defined vectors---two non-colinear vectors lying in the plane of the area. (By primitively defined vector, we mean a member of a properly defined vector space.)

Exactly the same thing goes for the unit normal vector. For example, \hat{k} is a basis vector, and thus, of course, a proper vector. However, if we want it to represent a unit surface area in the xy-plane, then something defining about that area has to be associated with this object. This we do via the relation \hat{k}= \hat{i}\times\hat{j} where "\times" denotes the cross product.

However, this is a bit of notation abuse, because we know that a cross-product is not a "true" vector; it's a pseudo-vector. The same object, viz. \hat{k}, appears in our equations sometimes as a proper vector and at other times as a pseudo-vector.

Since areas are pseudo-vectors, so must be stress, whether you define it as {n}[t] or as {A}[F], or even as a linear map. So long as areas are involved, it should turn out to be a "*pseudo*-tensor." Forces *are* proper vectors, and so are tractions (becuase they refer to only the magnitude of the area), but that's not enough.

We manage to get by treating the stress as a tensor (and the areas or the unit normals as vectors), primarily because all the relevant quantities are defined and used *at one and the same point. *The basic trouble with a pseudovector is that it cannot be freely transported. It has the meaning of a vector only at the point of its definition.

Now, look at Cauchy's formula, viz.,

"{t} = [\sigma]^T{n}".

This equation is nothing but saying that traction is the result of the dot product given by:

\vec{t} = \sigma \cdot \vec{n}.

In the first representation, the transpose-sign for the stress matrix appears simply because we are translating from the vector algebraic notation to the matrix notation. (This is exactly like saying: \vec{a} \cdot \vec{b} = {a}^T{b}.)

In either representation, what the equation basically says is that the projection of the stress (tensor) on to the specified unit normal (vector) is the traction (vector) acting on the specified side of the specified surface---at the specified point.

We can get by because all the quantities used in this equation, viz. {t}, [\sigma] and {n}, (or, if you prefer, {F}, [\sigma] and {A}) are defined, related and used at exactly one and the same point; they are never transported to (or used at) any other point. The projection occurs and is meaningful only at the single, distinguished, point.

This incidentally is the point I wanted to bring out and emphasize. Text-book derivations keep Cauchy's original line of thought completely intact. So, they make reference to the tetrahedral element. But as I said in the earlier reply, the tetrahedral element is a volume element, sort of. Actually, Cauchy's argument makes use of only the external, bounding *surfaces; *it does not refer to the interior or the volume region. Yet my objection remains: Cauchy's derivation of the above formula refers to four different planes *none* of which pass through the centroid of the tetrahedron. It's only because the derivation is for the limiting case of the vanishing region of space that the different planes can be seen as virtually crossing at the centroid point---only in the limiting case.

Now the point I want to emphasize is this: For Cauchy's formula to tumble out, you don't need to erect four different planes in the first place! Just take one plane passing through the point of interest (the single distinguished point), and rotate *the same* plane around that point any which way you wish. For example, rotate it so as to align along the xy plane, yz plane, etc. Since the plane always remains tucked on to the same distinguished point during any rotations, any and every quantity you define w.r.t. that plane and at that point, whether with this orientation of plane or that, escapes the trouble which the pseudovector faces due to "transportation." The weakness of text-book derivations (common to *all* text-books) is that, since all the four planes don't pass through a single point (say the centroid of the tetrahdron), the area vectors are implicitly assumed in their derivations as transported---which brings in the trouble of the pseudovector (and which trouble text-books summarily skip or ignore).

OK, enough for now. More, may be later.

====

Sorry for keeping you all waiting, but have been too busy (and will be, until Feb-end.) I will try to check out this thread before March arrives, but practically speaking, it may not be possible. However, I will definitely come back in early March, and so, please feel free to post your ideas, objections etc. in the meanwhile... Bye for now.

--Ajit

### I am preparing a new petition to parallel the UK strike in Italy

*In reply to UK university staff strike over pension changes – live*

The draft is here.

https://www.change.org/p/sergio-mattarella-diritto-di-sciopero-anche-per...

I hope that the UK example sets the scene for the dramatic problems in european universities, uncertain between the very liberal US model, and the classical state-based European model.

All italians, especially in UK, are welcome to give us suggestions for the new petition. Please contact me privately at mciava@poliba.it

### A paper in Nature on the italian election risks

*In reply to Corriere della Sera: recruitment in Italian Academia*

I recommend reading this paper in Nature on our italian election and the fact that very few if any parties give attention to science and research:

http://italianengineers.blogspot.it/2018/02/nature-scrive-un-articolo-sulle.html

### Re: stress definition

*In reply to Re: Stress Definition*

In the undergraduate linear algebra class, we introduced linear map about two weeks ago. From past experience, I know students need be reminded of what a map (i.e., a function) is. A map requires three sets: domain, codomain, and graph.

For a linear map, the domain must be a vector space, the codomain must be also a vector space, and the graph must be linear.

In saying the stress is a linear map, I stick to this prescription. Thus, the domain is the vector space of areas, the codomain is the vector space of forces, and the graph is the stress. That is your equation (3).

The Cauchy formula traction = (stress)(unit normal) does not follow this prescription. The collection of all unit normal vectors is not a vector space, because the addition of two unit normal vectors do not give another unit normal vector. Also, the collection of all traction vectors is not a vector space, because tractions on different planes are not additive.

Thus, in defining stress, I stick to your Equation (3).

In teaching the undergraduate course on linear algebra, I try to highlight the importance of the scalar set (i.e., the one-directional vector space). Then an n-dimension vector space is the Cartesian product of n scalar sets. A vector-vector linear map is a table of scalar-scalar linear map. Thus all linear map is similar to the fact of nature: a chicken has two feet. This fact is a linear map between two sets: the chicken set and the foot set.

Thus, reducing to one component, stress is just force per unit area. The algebra is similar to that each chicken has two feet.

In the linear algebra class, I then talked about two vector spaces: chicken-rabbit space and head-foot space. Then I talked about the vector-vector linear map: (chicken-rabbit space) → (head-foot space). The linear map is then a table (i.e., matrix) of four facts of life:

- A chicken has 1 head
- A chicken has 2 feet
- A rabbit has 1 head
- A rabbit has 4 feet

This strategy may be parallel to your way of introducing stress.

### Re: Defn of stress: A glaring mistake in my reply to Zhigang

*In reply to Re: Stress Definition*

Please ignore the second derivation, i.e., starting with Cauchy's formula, and proceeding as follows:

{t} = [\sigma]^T {n}

{t}[n] = [\sigma]^T {n}[n] (Post-multiply both sides by {n}-transposed)

{t}[n] = [\sigma]^T ({n}[n] is the dot product, equal to 1)** <------ THIS PART IS WRONG**

[\sigma] = {n}[t] (Take transposes of both sides, and flip LHS and RHS)"

=======

The error is in saying that {n}[n] is the dot product, equal to 1. Very elementary mistake!

=======

I wrote the reply while in office, interrupted by an inaugural function, some 10+ visitors, two meetings, quite a few phone-calls, and a skipped lunch... All simply because I am so enthusiastic about fundamental topics like these, that I can overboard.... But no excuses, so let me say sorry....

I also realize that the characterization of the stress-strain relation as a flux-gradient relation has a very definite merit to it, but the fact is, the strain tensor is just a part of the gradient tensor, not the entire one. I need to think more compreshensively about it.

========

Bye for now, I will go home, think a bit about it, and come back either tomorrow or the day after or so. In the meanwhile, everyone, feel absolutely free to leave your ideas for going from Cauchy's formula to a direct definition of stress, and please see if there is any other error in what I say. Thanks in advance for your feedback...

And sorry, once again, for bothering you all with the mistake....

--Ajit

### Re: Stress Definition

*In reply to Re: Stress is defined as the quantity equal to ... what?*

Dear Zhigang,

Wow, good to know that it's been puzzling for you too...

BTW, yes, I have been aware of your notes, and in fact recently recommended them in a reply at my personal blog, here [^].

Overall, to cut a long story short, here are a few points that I think we should be explaining to students:

====

We should state and explain the concept of stress as the direct end-result of a tensor product.

Here is one way to bring out the required direct definition. Only the UG-level matrix algebra is used.:

Notation: We adopt the convention that a vector is *always* denoted via a *column* vector, *never* using a row vector, and therefore, that a *row* vector *always* represents *only* a transposed vector. Column vectors are denoted using braces {c}, and row vectors and square matrices are denoted with square brackets [r] or [M]. (When using LaTeX, we use the left- and right-floor symbols for the row vectors, and the square brackets for matrices.)

First, define the local field of traction-vector acting on a given surface (whether the surface is internal or external, whether it is used in specifying BCs or not) in the usual way, viz., as the ratio \vec{F} / |\vec{A}| in the limit that |\vec{A}| vanishes. (Or, if you want to avoid limits at least initially, consider a uniform \vec{F} field.)

The denominator here is a scalar (it's only the magnitude of the area vector), and so, the division is not a problem. Basically, before using the area vector further, we isolate apart its two aspects, viz., the scalar magnitude and the direction.

Denote the unit normal to surface as {n} and its transpose as [n].

Start with the transpose of the traction vector, denoted as {t}^{T} and also written as [t].

[t] = [t] (and what else?)

= (1) [t]

= ( [n]{n} ) [t]

= [n] ( {n}[t] )

= [n] [\sigma]

In the last step, we have used the direct definition: [\sigma] \equiv {n}[t].

The above was the round-about way in which I had got to the defintion for the first time in my life. However, another, perhaps simpler, way is this. Start with Cauchy's formula:

{t} = [\sigma]^T {n}

{t}[n] = [\sigma]^T {n}[n] (Post-multiply both sides by {n}-transposed)

{t}[n] = [\sigma]^T ({n}[n] is the dot product, equal to 1)

[\sigma] = {n}[t] (Take transposes of both sides, and flip LHS and RHS)

The matrix-notation expression {n}[t] stands for a *tensor* product taken between the unit surface-normal vector on the left hand-side of the operator, and the traction vector on the right hand-side. Using the vector language, this tensor product is the same as what is expressed by: "\hat{n}\otimes\vec{t}".

This structure of

"{n} \otimes [the surface-intensity of a vector field variable]"

is common to all the *flux*-tensors of *all* the *vector* fields. *The direct definition of stress thus brings out the physical idea that the stress is the flux of the traction vector.*

The idea of the strain is obviously is based on a gradient; it's the symmetrical part of the displacement gradient.

The student can now appreciate that the stress-strain relation is nothing but just a case of a flux-gradient relation. The flux-gradient relations occur in almost *all* other areas of physics; as just one example, consider Fourier's law of heat conduction. So, hopefully, he can see the commonality of analysis with other branches of physics and engineering.

Speaking in general terms, the flux of a *scalar* field is a vector field; the gradient of a *scalar* field is a vector field; and the two vector fields are related via a material (constitutive) law.

Exactly similarly, the flux of a *vector* field is a tensor field; the gradient of a *vector* is a tensor field; and the two tensor fields are related via a constitutive law.

===

The idea that the stress is a linear map, as emphasized by you, is indeed very helpful. It throws light on what kind of purpose it serves. So, it is very valuable.

That's what the indirect equation

{t} = [\sigma]^T {n} (i.e. Cauchy's formula)

shows. It brings out, very clearly, the fact that the stress as a mathematical object is, from the external viewpoint, a linear map (from {n} to {t})

However, IMHO, this idea also should be complemented by pointing out that the stress is a tensor product (which highlights its internal structure) and that it is a flux (which identifies its physical meaning). The direct definition allows one to see both these latter facts.

===

BTW, the idea of a flux does not always refer to something that flows; it can refer to something that simply exists (rather than flows across) a surface. The idea of flux, however, necessarily refers to a reference (planar) surface.

Therefore, the flux nature of stress also helps reinforce the idea that it is purely a surface phenomenon. To define stress, all that you need is a planar element (whose orientation can be made to change) around the point of interest. In particular, you *don't* need a volume element at all. This is important to realize by the text-book writers. To define stress, you *don't* need either Cauchy's tetrahedron or the hexahedral element (as used in deriving the stress-divergence theorem). Both these are volume elements. But stress can be completely defined with just an orientable surface element. This point becomes clear only when you understand the stress as a flux, which itself becomes clear only after you consider the direct definition via tensor product of two vectors.

Finally, just one more point.

Stress analysis is based on the differential equation paradigm. For a problem involving only stresses (i.e., no equations or calculations of strains or displacements being involved), the auxiliary data for such a problem is fully stated in terms of just the unit normals and the traction vectors. The point to note is this: the auxiliary data in fact cannot be stated in any others terms. Specifically, it cannot be stated in terms of forces and areas. When in engineering we say that a force is being specified as a BC for a stress analysis problem, what we are actually doing is to mentally translate the force vectors into the area-intensity vectors, before importing them into the stress analysis problem as traction vectors. The direct definition simply helps makes this part more direct and explicit.

===

I have grown so convinced about the necessity to have a direct definition that I am seriously thinking of writing a journal paper on the topic, just to let the argument have a permanent place in the archives.

===

But, thanks, once again, for your interest,

Best,

--Ajit

### paper is accepted in Fatigue & Fracture of Engineering Materials

*In reply to On the connection between Palmgren-Miner’s rule and crack propagation laws*

Soon we can send you the final form.

MC

### Re: Stress is defined as the quantity equal to ... what?

*In reply to Stress is defined as the quantity equal to ... what?*

Ajit: Your question has also puzzeled me. I now favor your equation (3). Here is a post called "a state of stress is a linear map".

Incidentally, I am teaching undergarduate linear algebra now. Here are class notes that try to explain where we get vector spaces and linear maps.

### of course, it is in our to-do-list, but the idea came recently!

*In reply to BAM model and "Contact Challenge" surface*

You are not disrespectful at all. I agree with you.

The BAM model was validated, in the original paper, with pull-off data, which are much MORE difficult to predict with any other theory ---- including all Persson's theory.

The case of the Contact Challenge is relatively TRIVIAL, and with BAM model, given it is a very first approximation single closed form equation, I think we should be able to do it without any effort!

Let me talk to my collaborators if we find a couple hours free time.

### Re: VEMLab

*In reply to VEMLab: a MATLAB library for the virtual element method*

This one used to be visible at the front page of iMechanica until just this afternoon (IST).

Why was it taken off it? I wonder.

Quite unlike what this forum *used* to be like. ...

Best,

--Ajit

### BAM model and "Contact Challenge" surface

*In reply to by the way, I forgot to check if my BAM model works fine *

Dear Prof. Ciavarella,

I truly do not wish to be "cheeky" or disrespectful, but I find it remarkable that any researcher could refrain from the tantalising task of checking their own model against published data: is it not one of the most exciting aspect of modelling?

I hope you will find the time to check your BAM model with the "Contact Challenge" surface: regardless of the results it would certainly add value to this interesting discussion.

Best Regards

### BAM model and "Contact Challenge" surface

*In reply to by the way, I forgot to check if my BAM model works fine *

Dear Prof. Ciavarella,

I truly do not wish to be "cheeky" or disrespectful, but I find it remarkable that any researcher could refrain from the tantalising task of checking their own model against published data: is it not one of the most exciting aspect of modelling?

I hope you will find the time to check your BAM model with the "Contact Challenge" surface: regardless of the results it would certainly add value to this interesting discussion.

Best Regards

### Review with good friends top tribologists, including Muser

*In reply to a "contact sport" between academics*

Modeling and simulation in tribology across scales: An overview

http://imechanica.org/node/22143

## Recent comments