-
Notifications
You must be signed in to change notification settings - Fork 611
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 #1822
Comments
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Original issue reported on code.google.com by |
Yes, you're right. I'll fix. Thanks |
Refering to the topic: https://groups.google.com/forum/#!topic/fds-smv/YqEj7erosbw Is there a reason that copy-paste (from UG) results to problems in fds? I mean is it on purpose that this kind of apostrophe is used? Thank you. |
There might be incompatibilities sometimes with different programs and text editors, I recall for instance, I copied something into Latex file, and then found the apostrophes were not recognised and had to redefine them inside the latex Texmaker itself. There is a different when you are in code mode for example web design, you get it as ( ` ) Whereas in regular text it's as ( '). So, this is depending on the mode of your code you are using. For instance, on github here, when you use the < > for code, you get this special parenthesis for special code. |
Table 18.5 §18.24 SLCF
Thanks! |
Thanks for reporting these points. QUANTITY usually is considered as a title for the different output of temp, velocity etc.. Not sure what it has to do inside the table.
I would let other members to fix this since they know why it's there. |
Section 18.10.11 Fractional Effective Dose (FED) and Fractional Irritant Concentration (FIC) I think there is a typo in the fed_test.fds example, but I can't find it in the source so don't know where to check and comment (Basically, comma missing on the SLCF lines separating the QUANTITY and SPEC_ID) |
I think that 15.3 Background (User guide of SMV) should be in FDS User Guide instead of SMV. What do you think? |
I would rather keep it and along with other utilities such as smokezip and smokediff in the smokeview user's guide |
§16.3.1 = SPRAY_ANGLE(1,1:2), SPRAY_PATTERN_TABLE, It is detailed at great amount but is it possible to add few figures to explain the parameters above by showing which angles they correspond? |
Is this in the FDS User Guide? Are you looking at the latest guide? |
Yes User Guide, This is the info on the cover page of the document: January 18, 2017 |
You can check the latest files here. |
For development purposes use the nightly builds. See the link here at the
bottom:
https://pages.nist.gov/fds-smv/manuals.html
…On Tue, Jul 25, 2017 at 10:22 AM, Ersin9y714 ***@***.***> wrote:
Yes User Guide,
How can I check the most up to date file?
This is the info on the cover page of the document:
January 18, 2017
FDS Version 6.5.3
Revision: FDS6.5.3-569-ge3d0d6c
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AENrwZLmWIErCam9O0pXyHeJfpfNJV-Nks5sRfohgaJpZM4FMHuB>
.
|
First time I see this link. Thank you! Is there any way to see the changelog of these new versions of the Guides? The link on the front page directing me to the FDS4 user guide. Is that normal? I thought I would find figures about my request in the up-to-date guide but I do not see. Please let me know if I miss it or is it a good idea to add or not. Thank you |
Where do you get the "link on the front page"? Both links that Salah and I
sent you seem to work for me to get you to the development version of the
guides.
…On Tue, Jul 25, 2017 at 10:35 AM, Ersin9y714 ***@***.***> wrote:
First time I see this link. Thank you!
Is there any way to see the changelog of these new versions of the Guides?
The link on the front page directing me to the FDS4 user guide. Is that
normal?
http://dx.doi.org/10.6028/NIST.SP.1019
I thought I would find figures about my request in the up-to-date guide
but I do not see. Please let me know if I miss it or is it a good idea to
add or not.
Thank you
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AENrwfca1nP5ZzpjiiDkoFiFbsZBtqicks5sRf1NgaJpZM4FMHuB>
.
|
Oh, that's the DOI, |
Interesting. Good catch. I'll see if we can figure this out.
…On Tue, Jul 25, 2017 at 10:42 AM, Salah Benkorichi ***@***.*** > wrote:
Oh, that's the DOI,
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AENrwSjQL5DgVeJ8r4HdpCzcl5QfQU8Mks5sRf6_gaJpZM4FMHuB>
.
|
Yeah, normally, it should be linked with the latest version. Unless, it's set for a purpose. |
Could the compilation date and/or the SVN version also be included on the
front/third page so we know exactly which version we're looking at?
…On 25 July 2017 at 15:43, Salah Benkorichi ***@***.***> wrote:
Yeah, normally, it should be linked with the latest version. Unless, it's
set for a purpose.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOcJZYU6V_wNyszBWeFXEvBUvnasSRSBks5sRf8ggaJpZM4FMHuB>
.
|
Yes, they're included in the third page. Check my previous link for example July 26, 2017 |
Ah, yes. So it is - thought that was the FDS version release date! Might it
be worth explicitly noting it as "Manual complied on..."
…On 26 July 2017 at 11:53, Salah Benkorichi ***@***.***> wrote:
Yes, they're included in the third page. Check my previous link for example
July 26, 2017
FDS Version 6.5.3
Revision: FDS6.5.3-2166-gc88e7ce
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOcJZcopeJ-d4U61Yzp6xboPbQLWxidhks5sRxqSgaJpZM4FMHuB>
.
|
For the release document the date is the release date (or very close to it). The document that Salah cites is the nightly build. |
I thought it was locked to the release date. Given that the manual changes
quite a lot between releases, I think it might be good to make it clear -
and indicating on the 3rd page that the date is the compilation date of the
manual would assist, I think.
…On 26 July 2017 at 12:15, Randy McDermott ***@***.***> wrote:
For the release document the date is the release date (or very close to
it). The document that Salah cites is the nightly build.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOcJZQO3Alkxwr8VJeDw5nvOrO-Sb8P2ks5sRx-9gaJpZM4FMHuB>
.
|
The official release manual does not change. It is located here: https://pages.nist.gov/fds-smv/manuals.html These are the same documents that are downloaded with the bundle. |
Is there any way to see the changelog of these new versions of the Guides? It is hard to compare what is added/removed. |
You can access the change logs via GitHub. Navigate to the file and click
on the history button.
…On Aug 17, 2017 06:44, "Ersin9y714" ***@***.***> wrote:
Is there any way to see the changelog of these new versions of the Guides?
It is hard to compare what is added/removed.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#1822 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMNM8cYwj-APxVvZKb7fZyNSM15tqPtSks5sZBmSgaJpZM4FMHuB>
.
|
Closing this issue. If there are new typos, start a new issue. |
Original issue reported on code.google.com by
springcb38
on 2013-03-11 14:02:58The text was updated successfully, but these errors were encountered: