{"id":165606,"date":"2023-03-17T09:00:46","date_gmt":"2023-03-17T09:00:46","guid":{"rendered":"\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/"},"modified":"2023-07-31T12:31:35","modified_gmt":"2023-07-31T12:31:35","slug":"how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/","title":{"rendered":"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?"},"content":{"rendered":"<p>Two problems occur due to this error:  \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct  If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.<\/p>\n","protected":false},"template":"","class_list":["post-165606","topic","type-topic","status-publish","hentry","topic-tag-4431","topic-tag-mechanical-apdl","topic-tag-modal-harmonic-response","topic-tag-structural-dynamics","topic-tag-structural-mechanics"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Ansys Knowledge | Ansys Innovation Space\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge\" \/>\n\t\t<meta property=\"og:description\" content=\"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2023-03-17T09:00:46+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2023-07-31T12:31:35+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/topics\\\/#listItem\",\"name\":\"Topics\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/topics\\\/#listItem\",\"position\":2,\"name\":\"Topics\",\"item\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/topics\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic-tag\\\/structural-mechanics\\\/#listItem\",\"name\":\"structural-mechanics\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic-tag\\\/structural-mechanics\\\/#listItem\",\"position\":3,\"name\":\"structural-mechanics\",\"item\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic-tag\\\/structural-mechanics\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/#listItem\",\"name\":\"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/topics\\\/#listItem\",\"name\":\"Topics\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/#listItem\",\"position\":4,\"name\":\"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic-tag\\\/structural-mechanics\\\/#listItem\",\"name\":\"structural-mechanics\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/#organization\",\"name\":\"Ansys Knowledge\",\"description\":\"Ansys Innovation Space\",\"url\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/#webpage\",\"url\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/\",\"name\":\"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge\",\"description\":\"Two problems occur due to this error: \\u00e2\\u20ac\\u00a2The displacements and velocities of these new nodes are not initialized to zero \\u00e2\\u20ac\\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/forums\\\/topic\\\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\\\/#breadcrumblist\"},\"datePublished\":\"2023-03-17T09:00:46+00:00\",\"dateModified\":\"2023-07-31T12:31:35+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/#website\",\"url\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/\",\"name\":\"Ansys Knowledge\",\"description\":\"Ansys Innovation Space\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/innovationspace.ansys.com\\\/knowledge\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge","description":"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.","canonical_url":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BreadcrumbList","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge#listItem","position":1,"name":"Home","item":"https:\/\/innovationspace.ansys.com\/knowledge","nextItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/#listItem","name":"Topics"}},{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/#listItem","position":2,"name":"Topics","item":"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/","nextItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/#listItem","name":"structural-mechanics"},"previousItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/#listItem","position":3,"name":"structural-mechanics","item":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/","nextItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/#listItem","name":"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?"},"previousItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/#listItem","name":"Topics"}},{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/#listItem","position":4,"name":"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?","previousItem":{"@type":"ListItem","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/#listItem","name":"structural-mechanics"}}]},{"@type":"Organization","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/#organization","name":"Ansys Knowledge","description":"Ansys Innovation Space","url":"https:\/\/innovationspace.ansys.com\/knowledge\/"},{"@type":"WebPage","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/#webpage","url":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/","name":"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge","description":"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/innovationspace.ansys.com\/knowledge\/#website"},"breadcrumb":{"@id":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/#breadcrumblist"},"datePublished":"2023-03-17T09:00:46+00:00","dateModified":"2023-07-31T12:31:35+00:00"},{"@type":"WebSite","@id":"https:\/\/innovationspace.ansys.com\/knowledge\/#website","url":"https:\/\/innovationspace.ansys.com\/knowledge\/","name":"Ansys Knowledge","description":"Ansys Innovation Space","inLanguage":"en-US","publisher":{"@id":"https:\/\/innovationspace.ansys.com\/knowledge\/#organization"}}]},"og:locale":"en_US","og:site_name":"Ansys Knowledge | Ansys Innovation Space","og:type":"article","og:title":"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge","og:description":"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error.","og:url":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/","article:published_time":"2023-03-17T09:00:46+00:00","article:modified_time":"2023-07-31T12:31:35+00:00","twitter:card":"summary_large_image","twitter:title":"How to resolve Class3 Error 2005-13 if it has already occurred in the database? Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error? | Ansys Knowledge","twitter:description":"Two problems occur due to this error: \u00e2\u20ac\u00a2The displacements and velocities of these new nodes are not initialized to zero \u00e2\u20ac\u00a2The record size of these new nodes are not correct If the error already is in the database, issuing an ICDELE and then defining new ICs will cleanly correct the error."},"aioseo_meta_data":{"post_id":"165606","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"limit_modified_date":false,"created":"2025-10-17 22:20:47","updated":"2026-07-29 17:42:06","ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/innovationspace.ansys.com\/knowledge\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/\" title=\"Topics\">Topics<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/\" title=\"structural-mechanics\">structural-mechanics<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tHow to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/innovationspace.ansys.com\/knowledge"},{"label":"Topics","link":"https:\/\/innovationspace.ansys.com\/knowledge\/topics\/"},{"label":"structural-mechanics","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic-tag\/structural-mechanics\/"},{"label":"How to resolve Class3 Error 2005-13 if it has already occurred in the database?  Class3 Error 2005-13 states that if new nodes are defined after an IC command, and those new node numbers are larger than the largest node number that was active when the IC command was issued, the initial conditions input by the second and any subsequent IC commands are not correctly defined for all those nodes with larger node numbers. This Class3 report goes on to give two workarounds that are helpful for cases where this error has not already occurred. However, no workaround is given to help someone who already has this error in their database. What can I do if my database already contains this error?","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/how-to-resolve-class3-error-2005-13-if-it-has-already-occurred-in-the-database-class3-error-2005-13-states-that-if-new-nodes-are-defined-after-an-ic-command-and-those-new-node-numbers-are-larger-th\/"}],"acf":[],"custom_fields":[{"0":{"_wp_page_template":["default"],"_bbp_last_active_time":["3\/15\/2023 20:20"],"_bbp_forum_id":["27792"],"_bbp_author_ip":["23.56.168.180"],"_btv_view_count":["853"],"siebel_km_number":["423857"],"product_version":["17"],"km_published_date":["2005-08-03T00:00:00.000Z"],"family":["Structural Mechanics"],"application_name":["Mechanical APDL"]},"test":"articlesansys-com"}],"_links":{"self":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics\/165606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics"}],"about":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/topics\/165606\/revisions"}],"wp:attachment":[{"href":"https:\/\/innovationspace.ansys.com\/knowledge\/wp-json\/wp\/v2\/media?parent=165606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}