cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Kastchei
‎05-14-2024
  • 127 Posts
  • 70 Likes Given
  • 2 Solutions
  • 25 Likes Received

Re: SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-14-2024 11:46 AM
‎05-14-2024 11:46 AM
@DanH_sas wrote: Just to make sure this is an "apples-to-apples" comparison, can you generate the output using the WORD destination and set the OUTPUTFMT on the ODS GRAPHICS statement to be SVG? The default DPI for PDF output is 150dpi, whereas WORD is using either 96 or 100dpi. That might be causing variation. Hi Dan.  I tried with the Word destination; however, I got the following warnings.   WARNING: The ODS WORD destination is preproduction in this release. WARNING: Word destination does not support SVG images. Using the default static format. The same difference in font size occurs between gTitle and noGTitle.  That's seen in [test side-by-side Word destination.docx].  Is there another outputFmt you would suggest to try rather than the default static format?   Edit: I tried EMF, and that seems to have fixed the issue.  Now, the comparison looks more or less the same size, just with different smoothing.  That's the [test side-by-side Word EMF.docx] attachment. ... View more

Re: SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-10-2024 02:42 PM
‎05-10-2024 02:42 PM
@ballardw wrote: Please describe the tool you are using to determine the font sizes. Not saying you are wrong but the limited tools I have for examining the created document show other values than you get though still not the specified. I copied formatted text for Title 1 and pasted into a Word document which let me see the font and size of 12.5 for example. And font for the X axis labels isn't Arial.   You may need the ODS GRAPHICS/ noscale ; option. Maybe. Supposedly the scaling only changes when you set different Width and/or Height options but since you are seeing some different results for title and footnote text it may be worth trying. I did the same as you.  I copied the text from the PDF to Word which gave the font point sizes I mentioned.  Interesting that you aren't getting the same ones!  I also see that the labels for the axes (both X and Y) are not Arial but Albany AMT.  (Although on my machine those two fonts look identical.)   @Jay54 wrote: Try using ods graphics on / scale=off; See last paragraph here: https://documentation.sas.com/doc/en/vdmmlcdc/8.1/grstatproc/n0yadqm4wsfapgn1hzekfvu1ex0g.htm  Like you both suggest, I tried noScale.  Same problem.   @Cynthia_sas wrote: Hi, My understanding is that the Microsoft name for the Arial font is not the correct way to specify the font for the PDF location. When I need to specify Arial or an Arial-like font for a PDF file, I always use Arial Unicode MS or Albany AMT or Helvetica with PDF. For more information about Arial and PDF, read the article "The Scourge of Arial" https://www.marksimonson.com/notebook/view/the-scourge-of-arial . Cynthia At Cynthia's suggestion, I switched font faces.  I changed to HelveticaNeueforSAS and to Albany AMT.  The font face does change, but the same size problems persist.  They are consistent at least, so 12pt upscales to 13pt with all three fonts: Arial, HelveticaNeueforSAS, and Albany AMT.  I think we're narrowing the issue down to an SGPlot rendering issue.  Perhaps there is some scaling happening despite the noScale option? ... View more

SGPLOT producing wrong font sizes

by Pyrite | Level 9 in Graphics Programming
‎05-10-2024 11:53 AM
‎05-10-2024 11:53 AM
Howdy!   If I specify a font size in SGPLOT, SAS does not seem to actually produce that font size in ODS PDF.  It seems to produce some larger font size.  Here's example code.   ods pdf file = "M:\test.pdf"; ods graphics on / reset; title1 height = 12pt font = 'Arial' 'Title 1'; title2 height = 11pt font = 'Arial' 'Title 2'; title3 height = 10pt font = 'Arial' bold 'Title 3'; footnote1 height = 9pt font = 'Arial' 'Footnote 1'; footnote3 height = 8pt font = 'Arial' 'Footnote 2'; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 9.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 10pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 10.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 11pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 11.5pt); run; proc sgplot data = sasHelp.class; series x = name y = age; xAxis valueAttrs = (family = 'Arial' size = 12pt); run; ods pdf close; Title1 comes out as 13 pt. Title2 as 11.5 pt. Title3 as 11 pt. Footnote1 as 9.5 pt. Footnote2 as 9 pt. The x-axis tick values come out as 9.5, 11, 11, 11.5, 11.5, and 13 pt. respectively.   If I add  noGTitle and  noGFootnote  to the ODS PDF statement, then the font sizes for the titles and footnotes are correct.  It seems the problem is with the graphic procedure itself.   I checked the font sizes by copying the text from the PDF and pasting into Word.  I am fairly certain the same happens with ODS RTF; I can't paste the text into Word, but eyeballing it, it looks the same.  Attached are the PDF and RTF outputs each way, plus a screenshot of the side-by-side comparison of the two RTF files showing that the font without noGTitle definitely is bigger than the font with noGTitle.   Does anyone else also get this?  I tested on a SAS session with no other options, custom configuations, etc. but maybe there's still something set on my machine that is messing it up.   Best regards, Michael       ... View more

Stop log from clearing

by Pyrite | Level 9 in SAS Enterprise Guide
‎10-25-2023 03:58 PM
‎10-25-2023 03:58 PM
Howdy, SASers,   My work has moved from SAS code into EG.  However, each time I run a section of code, the log is first cleared.  Thus, the log from any previous sections of the code submitted are lost.  For example, I'll run lines 1-100 and then check output.  I'll then run lines 101-200, and check output again.  At this point, the log only shows lines 101-200, and not everything from 1-200.  Assuming my program has 2000 lines, by the end, I might have a log that only shows the last 10 lines.   Is there any setting to make the log persist when running line-by-line, so that every SAS code that was submitted is shown along with associated notes, warnings, and errors?  Essentially, I want the log to work like it does in SAS.   Thanks! Michael ... View more

Warning with proc FREQ and list outcum options

by Pyrite | Level 9 in SAS Procedures
‎10-13-2023 03:24 PM
‎10-13-2023 03:24 PM
proc freq data = sasHelp.class;     tables Sex*Age / list out = ___temp outCum; run; WARNING: The OUTCUM option is available only for one-way and LIST tables. Should this warning say WARNING: The OUTCUM option is available only for one-way tables. or have I misunderstood the list option?   The output dataset does not have the cumulative variables, although the ODS output does.  The same happens on colleagues' machines.   SAS 9.4 TS Level 1M6 X64_10PRO platform Windows Version 1.0.19041 ... View more

Re: Reset Windows file associations from Enterprise Guide back to base...

by Pyrite | Level 9 in SAS Enterprise Guide
‎07-19-2023 10:50 AM
1 Like
‎07-19-2023 10:50 AM
1 Like
Thank you!!  The registry edit program at the bottom worked for me. ... View more

Reset Windows file associations from Enterprise Guide back to base SAS...

by Pyrite | Level 9 in SAS Enterprise Guide
‎07-18-2023 01:04 PM
‎07-18-2023 01:04 PM
Hello!   IT just updated my Enterprise Guide, and this commandeered all my file type associations in Windows.  For example, if I double-click on class.sas7bdat from Windows Explorer, it opens in Enterprise Guide, and I want it to open in base SAS 9.4.   Windows 10 Enterprise Version 21H2 SAS for Windows SAS 9.4 TS Level 1M6 X64_10Pro platform   I tried right-clicking and selecting "Open with..." and then navigating to C:\Program Files\SASHome\SASFoundation\9.4 and selecting sas.exe.  This does not work.  SAS starts to open with the splash screen, but then it disappears and a log file is created in the folder with the dataset.  The log is attached and pasted below as well.  Also, the icon on the file no longer looks like a little database, but instead is the blue SAS shortcut icon.   In the past, when I've double-checked on a SAS dataset, it would open SAS first, if needed, then assign a library like TMP1, TMP2, TMP3, etc. for the Windows folder, and then open the dataset from that library.  I would like to get that functionality back.   Thanks!   Here's that log that was created, called class.sas7bdat.log (I had to append .txt to the attachment to get the website to upload it).   1 The SAS System 12:58 Tuesday, July 18, 2023 NOTE: Unable to open SASUSER.REGSTRY. WORK.REGSTRY will be opened instead. NOTE: All registry changes will be lost at the end of the session. WARNING: Unable to copy SASUSER registry to WORK registry. Because of this, you will not see registry customizations during this session. NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead. NOTE: All profile changes will be lost at the end of the session. NOTE: Copyright (c) 2016 by SAS Institute Inc., Cary, NC, USA. NOTE: SAS (r) Proprietary Software 9.4 (TS1M6) Licensed to MOUNT SINAI SCHOOL OF MEDICINE - SFA T&R, Site 70100937. NOTE: This session is executing on the X64_10PRO platform. NOTE: Analytical products: SAS/STAT 15.1 SAS/ETS 15.1 SAS/OR 15.1 SAS/IML 15.1 SAS/QC 15.1 NOTE: Additional host information: X64_10PRO WIN 10.0.19041 Workstation NOTE: SAS initialization used: real time 1.02 seconds cpu time 0.31 seconds WARNING: Truncated record. WARNING: A line of input contains one or more null (hexadecimal 00) characters, which might cause the SAS System to ignore part of the line. The line, with null characters printed as question marks, is: 1 Âê`³Ͻ’ Ç1Œ"" 332 "" 3323#3   SAS __ 180 1 ! FILECLASS DATA 1 ! Ñ"«^جÛAÑ"«^جÛA ”ÑÀ ”ÑÀ    9.0401M6X64_SR12R2 1 ! Ñ"«^lÄ;lÄ;lÄ; 1 ! 8Žp³ Ñ"«^جÛA 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 2 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 3 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 4 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 5 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 6 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 7 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 8 The SAS System 12:58 Tuesday, July 18, 2023 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! 1 ! ERROR 180-322: Statement is not valid or it is used out of proper order. 217: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 217-322: Invalid statement due to first character being unprintable (hexadecimal representation: 9D). 217: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 217-322: Invalid statement due to first character being unprintable (hexadecimal representation: 9D). 180: LINE and COLUMN cannot be determined. NOTE: NOSPOOL is on. Rerunning with OPTION SPOOL might allow recovery of the LINE and COLUMN where the error has occurred. ERROR 180-322: Statement is not valid or it is used out of proper order. ERROR: Errors printed on pages 1,8. NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414 NOTE: The SAS System used: real time 1.02 seconds cpu time 0.31 seconds   ... View more

Re: Comparing custom contrasts when interaction is not significant

by Pyrite | Level 9 in Statistical Procedures
‎03-27-2023 06:07 PM
‎03-27-2023 06:07 PM
Thank you!  And duh!  I don't know why I just didn't make a combined variable.  It's so obvious now, haha. ... View more

Comparing custom contrasts when interaction is not significant

by Pyrite | Level 9 in Statistical Procedures
‎03-24-2023 11:03 AM
‎03-24-2023 11:03 AM
Hello, everyone!   I have a model that incorporates race as (Whites vs other) and ethnicity as (Hispanic vs not).  The PI wants to look at non-Hispanic Whites vs all others as a contrast.  This is easily enough done by including the interaction in the model and writing: lSMestimate race2*hispanic2 'All Others vs. Non-Hispanic White' 1 -3 1 1 / divisor = 3; It turns out that this interaction is very not significant (Type 3 p = 0.70).  I realize that the interaction staying in the model while not significant is not likely to affect my results much.  But if I did want to remove the interaction from the model and rerun, could I still do the same comparison: non-Hispanic Whites vs all others?  I've written this code, and it's estimable, but my hunch is that theoretically, the model can no longer say anything about a combination of the two groups, even though I technically can form the estimates and compare their difference. *estimate 'Hispanic Non-White' intercept 1 race2 0 1 hispanic2 1 0; *estimate 'Non-Hispanic Non-White' intercept 1 race2 0 1 hispanic2 0 1; *estimate 'Hispanic White' intercept 1 race2 1 0 hispanic2 1 0; estimate 'Avg. of All Others' intercept 3 race2 1 2 hispanic2 2 1 (divisor = 3), 'Non-Hispanic White' intercept 1 race2 1 0 hispanic2 0 1, 'Avg. of All Others vs. Non-Hispanic White' race2 -2 2 hispanic2 2 -2 (divisor = 3); This does give an answer in the same ballpark as the model with the interaction, which might be expected since the interaction was not significant.   My reason for asking is because my real model has 8 racial groups and 3 ethnicity groups, and running the model with an interaction is not possible (quasi-complete separation in logistic).  I dichotomized race and ethnicity to get an answer to the study question, but I am just curious if I could have kept the full responses, omitted the interaction, and still answer the question.  The answer I get when I do that is very different from either of the dichotomized answers above.  I want to understand if that difference is likely because what I did is invalid or if keeping all the detail about the other racial and ethnic categories might really have changed the result a lot.   Warm regards, Michael     ... View more

Input function requires length when informat does not

by Pyrite | Level 9 in SAS Programming
‎12-01-2022 05:23 PM
‎12-01-2022 05:23 PM
Howdy!   Could someone explain to me why the first datastep can read the date correctly with no length specified on the format (yymmdd.), but the second datastep using input() function cannot?  And why the behavior changes for mmddyy. but only if there are no leading zeros?   data _____1; informat x yymmdd.; input x; format x e8601Da.; cards; 2001-05-05 2001/5/5 ; run; data _____2; input x $ 10.; y = input(x, yymmdd.); z = input(x, yymmdd10.); format y z e8601Da.; cards; 2001-05-05 2001/5/5 ; run; proc print data = _____1; run; proc print data = _____2; run; data _____1; informat x mmddyy.; input x; format x e8601Da.; cards; 05/05/2001 5/5/2001 ; run; data _____2; input x $ 10.; y = input(x, mmddyy.); z = input(x, mmddyy10.); format y z e8601Da.; cards; 05/05/2001 5/5/2001 ; run; proc print data = _____1; run; proc print data = _____2; run; Output Obs x 1 2001-05-05 2 2001-05-05 Obs x y z 1 2001-05-05 . 2001-05-05 2 2001/5/5 . 2001-05-05 Obs x 1 2001-05-05 2 2001-05-05 Obs x y z 1 05/05/2001 . 2001-05-05 2 5/5/2001 2020-05-05 2001-05-05 Warm regards, Michael ... View more

SAS equivalent of R orm

by Pyrite | Level 9 in Statistical Procedures
‎10-10-2022 02:11 PM
‎10-10-2022 02:11 PM
Hello,   I am wondering if there is SAS equivalent to the orm package for R.  orm is the ordinal regression models package for semi-parametric models of continuous outcomes, as opposed to OLS or a binary/multinomial outcome.  The details are described in these course notes, Section 11.4 Ordinal Regression Models for Continuous Y.   https://hbiostat.org/doc/rms.pdf    Or would I need to code these models with NLMixed?   Thanks! Michael ... View more

Re: Suppress writing composite index to log

by Pyrite | Level 9 in SAS Programming
‎02-09-2021 10:24 PM
‎02-09-2021 10:24 PM
It suppresses notes that begin with INFO:, but it does not, sadly, suppress the index variables being listed out.  I edited my post to include that. ... View more

Suppress writing composite index to log

by Pyrite | Level 9 in SAS Programming
‎02-09-2021 09:54 PM
‎02-09-2021 09:54 PM
Hello!   I have a SAS dataset with a composite index.  I'm running a SAS procedure (StdRate) over it many times, and I'm looking to suppress information being written to the log so that it doesn't fill it up and pause.  I have noNotes, noSource, and msgLevel = i, and that gets rid of everything except the list of variables that make up the index being used.   Here is the log for one call without anything suppressed: 38 proc stdRate data = analysis.nSummarizeT (where = (<snipped>) 39 refData = analysis.qUSCensusFormatted (where = (<snipped>) 40 method = direct stat = rate(mult = 100000) effect = ratio 41 alpha = 0.05 CL = gamma(type = average) 42 plots = all; INFO: Index unique1 selected for WHERE clause optimization. 43 by levelN level groupN group exposureTypeN exposureType _type_ consentFirst remove; 44 45 population group = exposureHigh event = events total = personYears; 46 reference total = population; 47 strata gender ageGroup / effect stats(cl = poisson) order = data; INFO: Use of index unique1 for WHERE clause optimization canceled. INFO: Index index selected for WHERE clause optimization. INFO: Index index selected for BY clause processing. NOTE: An index was selected to execute the BY statement. The observations will be returned in index order rather than in physical order. The selected index is for the variable(s): levelN level groupN group exposureTypeN exposureType _type_ consentFirst remove 48 ods output StdRate = ___StdRate (compress = no) Effect = ___Effect (compress = no); 49 run; NOTE: The data set WORK.___EFFECT has 1 observations and 19 variables. NOTE: The data set WORK.___STDRATE has 2 observations and 21 variables. NOTE: PROCEDURE STDRATE used (Total process time): real time 0.63 seconds user cpu time 0.14 seconds system cpu time 0.17 seconds memory 11344.90k OS Memory 86928.00k Timestamp 02/09/2021 09:40:35 PM Step Count 9281 Switch Count 0 Here is the log for several calls with noNotes, noSource, and msgLevel = i: levelN level groupN group exposureTypeN exposureType _type_ consentFirst remove levelN level groupN group exposureTypeN exposureType _type_ consentFirst remove levelN level groupN group exposureTypeN exposureType _type_ <etc.> Is there any way to prevent SAS from printing these index variables?   Warm regards, 🙂 Michael   ... View more

Re: Scientific notation and numeric precision

by Pyrite | Level 9 in SAS Programming
‎12-24-2020 02:36 PM
‎12-24-2020 02:36 PM
Thank you both for the detailed explanations and the simulations! This was way more helpful than I was expecting. I am comparing two ways to round to significant figures. One was extremely simple: input(put(x, E9.), E9.) The other used some log10 and other math to determine which decimal place is needed for the second argument of the round function. I wasn't so surprised to see differences for extremely small values, but some of the ones in my original post, like 7.27E0, where surprising. From my own experimenting, it seems that the scientific notation version works a little better for very large numbers: that is, it's exact for slightly more magnitudes of order, whereas the round seems to have a mixup along the way. Thanks again. Happy holidays! Warm regards, Michael ... View more

Scientific notation and numeric precision

by Pyrite | Level 9 in SAS Programming
‎12-22-2020 01:23 PM
1 Like
‎12-22-2020 01:23 PM
1 Like
Hello!   I understand a little bit about floating point storage; however, could someone explain these results?  I can understand a number not being stored exactly due the the precision of the system and how that leads to conflict in calculations sometimes.  I'm a little confused how these two representations of the same number that do not include any calculations get stored differently.  Is SAS turning scientific notation into a calculation rather than just moving the decimal place over?   Warm regards, Michael 3452 data _null_; 3453 if 727 = 7.27E2 then put 'Equal'; else put 'Unequal'; 3454 if 72.7 = 7.27E1 then put 'Equal'; else put 'Unequal'; 3455 if 7.27 = 7.27E0 then put 'Equal'; else put 'Unequal'; 3456 if 0.727 = 7.27E-1 then put 'Equal'; else put 'Unequal'; 3457 if 0.0727 = 7.27E-2 then put 'Equal'; else put 'Unequal'; 3458 if 0.00727 = 7.27E-3 then put 'Equal'; else put 'Unequal'; 3459 if 0.000727 = 7.27E-4 then put 'Equal'; else put 'Unequal'; 3460 if 0.0000727 = 7.27E-5 then put 'Equal'; else put 'Unequal'; 3461 put '---'; 3462 if 0.0000727 = round(7.27E-5 , 1E-16) then put 'Equal'; else put 'Unequal'; 3463 if 0.0000727 = round(0.0000727, 1E-16) then put 'Equal'; else put 'Unequal'; 3464 if 7.27E-5 = round(7.27E-5 , 1E-16) then put 'Equal'; else put 'Unequal'; 3465 run; Equal Equal Unequal Equal Equal Equal Equal Unequal --- Equal Equal Unequal Here's another example that I don't understand. 3701 data _null_; 3702 if 7900000000000000000 = round(7900000000000000000, 1000000000 ) then put 'Equal'; else put 'Unequal'; 3703 if 7900000000000000000 = round(7900000000000000000, 10000000000 ) then put 'Equal'; else put 'Unequal'; 3711 run; Equal Unequal     ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎05-14-2024 03:31 PM
Group Hubs for Kastchei
View All
Likes given to
Likes from
Quick links