24小时热门版块排行榜

返回列表

当前只显示满足指定条件的回帖，点击这里查看本话题的所有回帖

mafeng0907

捐助贵宾 (初入文坛)

应助: 0 (幼儿园)
金币: 704.9
散金: 13
帖子: 41
在线: 36.1小时
虫号: 1400888
注册: 2011-09-14
性别: GG
专业: 可再生与替代能源利用中的

[求助] 怎样解决FLUENT received fatal signal (ACCESS_VIOLATION)的错误？已有2人参与

大家好我是初学者现在希望用fluent做一个热湿迁移的问题，加载一个UDF到fluent 但是每次迭代总是报错：
Error:
FLUENT received fatal signal (ACCESS_VIOLATION)
1. Note exact events leading to error.
2. Save case/data under new name.
3. Exit program and restart to continue.
4. Report error to your distributor.
Error Object: ()
case文件和udf程序已上传，我一直找不到其中错误的原因，因为udf在另外一个模型中能够使用并且收敛，而网格是简单的结构化网格，请大家指点

回复此楼

» 本帖附件资源列表

欢迎监督和反馈：小木虫仅提供交流平台，不对该内容负责。
本内容由用户自主发布，如果其内容涉及到知识产权问题，其责任在于用户本人，如对版权有异议，请联系邮箱：xiaomuchong@tal.com
附件 1 : muben100_zuizhong.cas

2012-04-10 13:49:45, 457.75 K

附件 2 : zuizhong.c

2012-04-10 13:50:03, 13.19 K

» 本帖已获得的红花（最新10朵）

mafeng0907

» 猜你喜欢

40+中年人失业后，还能找到好工作吗？已经有15人回复
二审4个多月了还是Awaiting Reviewer Scores 已经有5人回复
申请科研项目纯靠实力能成功吗？已经有12人回复
用NBS溴化时溶剂除了CCl4外还有什么已经有6人回复
极限拉扯，如何抉择已经有15人回复
OpenAI又攻克数学难题了，离AI做有机合成还有多远？已经有13人回复
课题组会帮你通过考核么？已经有7人回复
招收博士生一名已经有3人回复

1楼 2012-04-10 13:55:13

已阅回复此楼关注TA 给TA发消息送TA红花 TA的回帖

seasky71

木虫 (知名作家)

应助: 1 (幼儿园)
金币: 33791.2
散金: 116
红花: 4
沙发: 1
帖子: 5537
在线: 311.3小时
虫号: 303114
注册: 2006-12-03
性别: GG
专业: 金属材料的凝固与结晶学

How do I resolve the following error: FLUENT received fatal signal (ACCESS_VIOLATION)?

This is the standard error caused by FLUENT trying to access data that has not been allocated.
There are several causes which we will discuss.

For example, in a UDF, you may probe the cell temperature using the macro C_T(c,t). However, if you have not turned the energy equation on, then there is NO temperature stored, and you will get an ACCESS_VIOLATION.

To check a Thread for whether a variable is stored on it, you can use the THREAD_STORAGE(t, SV_XXX) macro, where SV_XXX is the storage variable for the equation of interest. For the energy equation, you would use SV_T. This macro returns a pointer to the data. The value is NULL if the data is not available. See storage.h for a complete list of storage variables.

Another cause for the macro is that your case has a UDF hooked, but you do not have the UDF available. The solution is to make sure you have the UDF directory in the correct location relative to the case file.

The usual situation is that you udf has problems.