Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

typo in UG #5585

Closed
Er9y714 opened this issue Oct 18, 2017 · 9 comments
Closed

typo in UG #5585

Er9y714 opened this issue Oct 18, 2017 · 9 comments
Assignees

Comments

@Er9y714
Copy link

Er9y714 commented Oct 18, 2017

  • FIXED_MIX_TIME is not on the 19.23 REAC section.

  • RESEARCH_MODE is not in the user guide.

  • Smokeview> right click >Help> Shortcuts >the last line, there is a description but not the key (&) for anti-aliasing.

Thank you.

@sbenkorichi
Copy link
Collaborator

Thanks,
somebody will take a look.

@rmcdermo
Copy link
Contributor

@Er9y714
Both FIXED_MIX_TIME and RESEARCH_MODE are hidden in the user guide on purpose (notice that the parameters are listed but comments out in the LaTeX source). The reason is that we do not want typical users playing with these parameters. RESEARCH_MODE is actually documented in the FDS Tech Guide (sec 3.2).

@rmcdermo
Copy link
Contributor

Oh, @gforney please look address the smv help menu question.

@gforney
Copy link
Contributor

gforney commented Oct 18, 2017

The short cut is & . help display is fixed in next version of smokeview that will be released (shortly). Note, all shortcuts are documented in Appendix C in the smokeview user's guide.

@Er9y714
Copy link
Author

Er9y714 commented Oct 19, 2017

In the latest releases;

Technical guide:
As an example, the critical adiabatic flame temperature can be assumed to have a constant value of
approximately 1600 K for hydrocarbon diffusion flames, as suggested by Beyler2.
User guide:
The default value is 1427 C (1700K). This value represents combustion of typical hydrocarbon fuels.

The temperature value is updated in userguide to 1700K from 1600K. Is there a reason for this update?

Also should I keep using this issue for typos or open a new one each time?

Thank you

@sbenkorichi
Copy link
Collaborator

Just open an issue each time you spot something as Kevin said last time.

@Er9y714
Copy link
Author

Er9y714 commented Oct 19, 2017

Sorry, I must have forgotten even if I read it. Opening a new issue. Thanks @sbenkorichi

@sbenkorichi
Copy link
Collaborator

Here :
Read his last comment after he closed it.
#1822

@Er9y714
Copy link
Author

Er9y714 commented Oct 19, 2017

Oh, I remember reading it, I thought he closed the issue because the post number in the issue increased too much. So, I thought he suggested opening a new issue until it reaches a certain length.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants