Why entangled melts and solutions differ in fast extensional flow

38

No. 1,272 in all physics · No. 86 in Soft Matter and Biological Physics

Non-expert version

In uniaxial extension of monodisperse entangled polystyrene at strain rates above the inverse Rouse time, melts show steady extensional viscosity $\eta_E \sim \mathrm{eps}_{dot}^{-1/2}$ while semidilute and concentrated solutions with matched entanglement number show extensional hardening, in conflict with tube models including chain stretch. Identify the mechanism (proposed: flow-induced reduction of monomeric friction by segment orientation) and predict $\eta_E(\mathrm{eps}_{dot})$ for melts and solutions from one theory.

What would settle it

A constitutive model with independently measured parameters that reproduces $\eta_{E}(eps_{dot})$ for melts and solutions, supported by rheo-optical or simulation measurements of the friction coefficient under flow.

Status in the literature

Steady thinning of PS melts in fast extension was reported in 2003 (Bach, Almdal, Rasmussen and Hassager, Macromolecules, https://doi.org/10.1021/ma034279q); the friction-reduction explanation is not universally accepted.

No solutions, ideas or subproblems yet.

How results are checked

See also

Comments (0)

Comments are not records: they are not signed, stamped or logged. How comments work

No comments yet.

Sign in to comment.

Details, signature and history
Kind
Phenomenon to explain
Answer
Mechanism
Posed
2003
Topic review
T. C. B. McLeish, Tube theory of entangled polymer dynamics, Advances in Physics, 2002. Link
Record
Revision 2 · notation repaired by the platform · compiled by AI, not yet reviewed by an editor
Batch approval
Approved for the batch by Victor Galitski (ORCID 0000-0001-5532-1096) · approval record · bundle This approves the batch, not each problem (what it means).
AI systems
AI systems used to prepare this seed revision, as listed in its record: ai:gpt-5.5 (how the seed revision was made)
Earlier revisions
revision 1 bundle

Proof

Fingerprint
5561b3e75091…
Public log
Entry 822, in checkpoint 2,123
In the log by
Block 969,698, 2026-10-03

This text was in the PubPhys log by that date. The date says nothing about when the problem was first posed.

History