Table des matières: :: Library Catalog

Enregistré dans:

Détails bibliographiques
Auteur principal:	Diego Ayala
Format:	Artículo científico
Langue:	es
Publié:	Universidad Centroccidental Lisandro Alvarado 2021
Sujets:	Ingeniería Out cargas ensayo Push conector ángulo Conectores de corte
Accès en ligne:	https://www.redalyc.org/articulo.oa?id=570367986005 https://www.redalyc.org/journal/5703/570367986005/ https://www.redalyc.org/journal/5703/570367986005/html/ https://www.redalyc.org/journal/5703/570367986005/570367986005.epub https://www.redalyc.org/journal/5703/570367986005/movil https://doi.org/10.13140/RG.2.2.18659.27684
Tags:	Ajouter un tag Pas de tags, Soyez le premier à ajouter un tag!

Table des matières:

Comparación del comportamiento entre conectores de corte angulares de diferentes espesores bajo cargas monotónicas y cíclicas Diego Ayala Carlos Chicaiza Luis Hernández Gabriel Velástegui Raúl Baquero Ingeniería Out cargas ensayo Push conector ángulo Conectores de corte Los conectores de acero tipo ángulo permiten la transferencia de efectos de corte en sistemas estructurales compuestos, específicamente en la interacción entre vigas metálicas y losas de hormigón armado. Estudiar el comportamiento mecánico de este tipo de conectores resulta indispensable por su amplio uso y difusión en la construcción, debido a su bajo costo y fácil instalación en obra. El presente artículo presenta un análisis experimental en 16 probetas ensayadas mediante el método Push-Out descrito por el Eurocódigo 4, comparando conectores angulares de 4 y 6 milímetros de espesor dispuestos en 2 posiciones diferentes cada uno, expuestos ante cargas monotónicas y cíclicas. La falla típica en los conectores fue por fractura del material base por encima del cordón de soldadura. La falla en el hormigón que provocaron los conectores Tipo 2 fue por aplastamiento de las losas mostrando grietas notorias en relación con los conectores Tipo 1 que generaron fisuras pequeñas. Los especímenes con conectores Tipo 1 de 6 mm fallaron por desprendimiento entre los conectores y las losas. Los conectores Tipo 2 resultaron ser los más dúctiles que los conectores Tipo 1. Los resultados indican que los conectores Tipo 2 obtuvieron un mejor comportamiento en términos de capacidad a cortante último, ductilidad y degradación de rigidez a corte. Los conectores Tipo 1 mostraron capacidades mecánicas inferiores. Finalmente, los resultados experimentales fueron evaluados con las ecuaciones teóricas propuestas por códigos constructivos e investigaciones similares. 2021 artículo científico 1856-9560 https://www.redalyc.org/articulo.oa?id=570367986005 https://www.redalyc.org/journal/5703/570367986005/ https://www.redalyc.org/journal/5703/570367986005/html/ https://www.redalyc.org/journal/5703/570367986005/570367986005.epub https://www.redalyc.org/journal/5703/570367986005/movil https://doi.org/10.13140/RG.2.2.18659.27684 es http://www.redalyc.org/revista.oa?id=5703 Gaceta Técnica application/pdf Universidad Centroccidental Lisandro Alvarado Gaceta Técnica (República Bolivariana de Venezuela) Num.2 Vol.22

if (filemtime($filename) + $maxlifetime < time()) { unlink($filename); $count++; } } return $count; } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ protected function saveSession($sessId, $data): bool { $sessFile = $this->path . '/sess_' . $sessId; if ($handle = fopen($sessFile, 'w')) { $return = false; // Lock the file for exclusive access to avoid issues with multiple // processes writing session simultaneously: if (flock($handle, LOCK_EX)) { $return = fwrite($handle, $data); // Make sure that there's no trailing data by truncating the file to // the correct length: ftruncate($handle, strlen($data)); fflush($handle); flock($handle, LOCK_UN); } fclose($handle); if ($return !== false) { return true; } } // If we got this far, something went wrong with the file output... // It is tempting to throw an exception here, but this code is called // outside of the context of exception handling, so all we can do is // echo a message.

// Anecdotal testing Today and Yesterday seems to indicate destroy() // is called by the garbage collector and everything is good. // Something to keep in mind though. return 0; } /** * Write function that is called when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ public function write($sessId, $data): bool { if ($this->writesDisabled) { return true; } return $this->saveSession($sessId, $data); } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ abstract protected function saveSession($sessId, $data): bool; }

* * @return void */ public function writeClose() { // The assumption is that we're using PHP's ext/session. // session_write_close() will actually overwrite $_SESSION with an // empty array on completion -- which leads to a mismatch between what // is in the storage object and $_SESSION. To get around this, we // temporarily reset $_SESSION to an array, and then re-link it to // the storage object. // // Additionally, while you _can_ write to $_SESSION following a // session_write_close() operation, no changes made to it will be // flushed to the session handler. As such, we now mark the storage // object isImmutable. $storage = $this->getStorage(); if (! $storage->isImmutable()) { $_SESSION = $storage->toArray(true); session_write_close(); $storage->fromArray($_SESSION); $storage->markImmutable(); } } /** * Attempt to set the session name * * If the session has already been started, or if the name provided fails * validation, an exception will be raised. * * @param string $name * @return SessionManager * @throws Exception\InvalidArgumentException */ public function setName($name) { if ($this->sessionExists()) { throw new Exception\InvalidArgumentException( 'Cannot set session name after a session has already started'

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
VUFIND_SESSION	"4865af931e52079dc0341f9e93820af9"
language	"fr"
ui	"standard"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1784609848.5102 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "4865af931e52079dc0341f9e93820af9" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1583}
SessionHelper	Laminas\Stdlib\ArrayObject {#1772}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"VUFIND_SESSION=4865af931e52079dc0341f9e93820af9; language=fr; ui=standard"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.85"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"44211"
REDIRECT_URL	"/Record/redalyc_570367986005/TOC"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/redalyc_570367986005/TOC"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1784609848.5058
REQUEST_TIME	1784609848

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
VUFIND_SESSION	"4865af931e52079dc0341f9e93820af9"
language	"fr"
ui	"standard"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1784609848.5102 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "4865af931e52079dc0341f9e93820af9" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1583}
SessionHelper	Laminas\Stdlib\ArrayObject {#1772}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"VUFIND_SESSION=4865af931e52079dc0341f9e93820af9; language=fr; ui=standard"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.85"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"44211"
REDIRECT_URL	"/Record/redalyc_570367986005/TOC"
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/redalyc_570367986005/TOC"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1784609848.5058
REQUEST_TIME	1784609848

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Documents similaires

Environment & details:

Environment & details: