forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Native %pl
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> ClearWin+
View previous topic :: View next topic  
Author Message
DanRRight



Joined: 10 Mar 2008
Posts: 2813
Location: South Pole, Antarctica

PostPosted: Sat Mar 18, 2017 4:41 pm    Post subject: Reply with quote

My observation is if, for example, scientist does not work on Saturdays - he does not work at all. Smile

Ken, Unless there was some specific purpose for that, copy_graphics_region was actually not needed to get 4 graphs together. Just placing these 4 %gr regions next to each other with ww[no_border] doing the same trick, is shorter and more convenient for run-time plotting. Here is the code example which running makes 4 different plots at the same time. It also crashes at the exit but the reason is probably different - program needs to exit cycling do loop first, which is probably easy to fix
Code:
winapp
use clrwin
common /RunContinueStop_/k_RunPauseContinueStop1234
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol
integer, external ::  Run

parameter (n=240)
integer x(n),y(n)
common x,y

k_RunPauseContinueStop1234 = 1
k_visual   = 1
ixVis       = 500
iyVis       = 360

ihGrVis      = 4
ihGrVisGreen   = 3
ihGrRun      = 2
ihGrMain   = 1

do i=1,n
 x(i)=5*i
 y(i)=150 - 100 * sin(i/10.)
enddo

 i=winio@('%bg[gray]&')
! i=winio@('%^tt[Run  Code]&',Run)
 i=winio@('%^tt[E&xit]%ff%nl&','+','set',k_RunPauseContinueStop1234, 4,'exit')
 i = winio@('%ww[no_border]%pv%fr%lw',1200,800, ictrlFrame)
 i=winio@('%aw%ww[no_border]%pv%60.5cw',ictrlFrame, 0)
 jj=Run ()

end
!=====================================================
integer*4 function Run ()
use clrwin
common /RunContinueStop_/k_RunPauseContinueStop1234
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol

integer, external ::  Vis, Calc,  Interrupt

j = Interrupt ()

 i=winio@('%ww[no_border]%ff&')
 i=winio@('%`gr[black]&',      ixVis, iyVis, ihGrMain)
 i=winio@('%`gr[blue]%ff&',    ixVis, iyVis, ihGrRun)
 i=winio@('%`gr[red]&',        ixVis, iyVis, ihGrVis )
 i=winio@('%`gr[green]',       ixVis, iyVis, ihGrVisGreen )

jj = Calc()

Run=1
end function

!================================================
integer*4 function Interrupt ()
use clrwin
common /RunContinueStop_/k_RunPauseContinueStop1234
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol
integer, external ::  Vis, Calc

 i=winio@('%^tt[Run]&',     'set',k_RunPauseContinueStop1234,1)
 i=winio@('%^tt[Pause]&',   'set', k_RunPauseContinueStop1234,2)
 i=winio@('%^tt[Continue]%ff&','set',k_RunPauseContinueStop1234,1)
 i=winio@('%^tt[StartVis]&','set',k_visual,1)
 i=winio@('%^tt[StopVis]&','set',k_visual,0)

 i=winio@('%^tt[E&xit]&', &
  '+', 'set',k_RunPauseContinueStop1234, 4, &
  '+', 'set',k_visual, 0, &
  '+', 'set',lw_visWindow, 0, &
       'set',iRunWindow,0) ! 'exit')

i=winio@('%lw&', iRunWindow)
Interrupt = 1
end function
!


Last edited by DanRRight on Sat Mar 18, 2017 10:28 pm; edited 8 times in total
Back to top
View user's profile Send private message
DanRRight



Joined: 10 Mar 2008
Posts: 2813
Location: South Pole, Antarctica

PostPosted: Sat Mar 18, 2017 10:08 pm    Post subject: Reply with quote

Code:
!================================================
integer*4 function Vis ()
use clrwin
common /RunContinueStop_/k_RunPauseContinueStop1234
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol
  i=winio@('%^tt[E&xit]&','set',lw_visWindow,0) ! 'exit')
  i=winio@('%lw',lw_visWindow)
  Vis = 1
end function
!=====================================================
integer*4 function Calc ()
use clrwin
common /RunContinueStop_/k_RunPauseContinueStop1234
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol
logical aa_log
integer, external :: plot
save

a = 0.1
ixold = 0
iyold = 0

1   call temporary_yield@()   

if(k_RunPauseContinueStop1234.eq.1) then

  ir = random() * 255
  ig = random() * 255
  ib = random() * 255
  print*,'IR,IG,IB=',IR,IG,IB

  if(k_visual.eq.1) then

  icol = rgb@(ir,ig,ib)

if(ir.lt.64) then
 Print*,'<16 Run',icol
 i16=select_graphics_object@(ihGrRun)
 if(i16.eq.0) goto 222
 call get_graphical_resolution@(ixVis,iyVis )

else if(ir.lt.128) then
  Print*,'<128 Main',icol
  i32=select_graphics_object@(ihGrMain)
  if(i32.eq.0) goto 222
  call get_graphical_resolution@(ixVis,iyVis )
  ix   = random() * ixVis
  iy   = random() * iyVis
  call DRAW_filled_RECTANGLE@(IX,IY,IXold,IYold,ICOL)
  goto 222

else if(ir.lt.196) then
  Print*,'<196 red',icol
  i48=select_graphics_object@(ihGrVis)
  if(i48.eq.0) goto 222
  call get_graphical_resolution@(ixVis,iyVis )
  ix   = random() * ixVis
  iy   = random() * iyVis
  call DRAW_RECTANGLE@(IX,IY,IXold,IYold,ICOL)

  goto 222

else
  Print*,'>196 green screen',icol
  i64=select_graphics_object@(ihGrVisGreen)
  if(i64.eq.0) goto 222
  call get_graphical_resolution@(ixVis,iyVis )
  jj = plot ()
  goto 222
 endif

  ix   = random() * ixVis
  iy   = random() * iyVis

  call temporary_yield@()   

  call draw_line@(ixold, iyold, ix,iy, icol)

222     ixold = ix
     iyold = iy
   endif

   endif

      do while(k_RunPauseContinueStop1234.eq.2)
     call temporary_yield@()   
     call sleep@(0.3)
          call sound@(8333,1)
      enddo

 if(k_RunPauseContinueStop1234.eq.4) goto 10000 ! stop run at exit button


  call sleep@(0.04)
  goto 1

10000   Calc = 1
end function
!........................................
integer function plot ()
use clrwin
parameter (n=240)
integer x(n),y(n)
common /Visual_/ k_visual, ixVis , iyVis, ihGrVis, ihGrVisGreen, lw_visWindow, ihGrRun, ihGrMain, icol
common x,y
save n_call, n1
data n_call/0/, n1/9/

   n_call = n_call + 1

   n1 = n_call
   if(n1.gt.n-1) then
     n_call = 1
          call clear_screen@()
        endif

   icol=rgb@(255,0,0)
   CALL set_line_width@(5)
   call draw_bezier@(x,y,n1,icol)

1000   plot = 1
   end
Back to top
View user's profile Send private message
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 7916
Location: Salford, UK

PostPosted: Mon Mar 20, 2017 11:32 am    Post subject: Reply with quote

New DLLs are now available via the following link. The usual cautions apply.
See the readme for new %pl options.
Please report any bugs but not requests for additional features.

https://www.dropbox.com/s/ycd80m06hx9uxys/newDLLs5.zip?dl=0
Back to top
View user's profile Send private message AIM Address
Kenneth_Smith



Joined: 18 May 2012
Posts: 697
Location: Hamilton, Lanarkshire, Scotland.

PostPosted: Mon Mar 20, 2017 9:23 pm    Post subject: Reply with quote

Paul,

Thanks for that - no exception on program exit now.

However, the problem with the curve fitting has come back to haunt us.

Using newdlls4 there is no overshoot in the step responses:-



But with the newdlls5 there is :-



I'm not worried about the aspect ratio - that can be fixed with the new %pl[margin=n], n = 30 looks about right to me, and the %pl[etched] is a nice touch.

Hope this is an easy fix for you. The new %pl just about does everything I need it to do now.

Thanks

Ken
Back to top
View user's profile Send private message Visit poster's website
Kenneth_Smith



Joined: 18 May 2012
Posts: 697
Location: Hamilton, Lanarkshire, Scotland.

PostPosted: Mon Mar 20, 2017 9:47 pm    Post subject: Reply with quote

Dan,

Thanks for your sample code. It is always interesting to see other peoples approaches. I realise that I have much to learn having spent a few hours reading the Clearwin+ help pages after working my way through your code.

Generally my programs (some written 25 or more years ago) do a lot of number crunching and then spit out some results. My motivation for using Clearwin and FTN95 stems from the fact that younger engineers will not prepare a text file for input to a program, or accept a long file with many columns of data as an output. Since I started using Clearwin I have actually got some of our younger graduate engineers interested in writing Fortran rather than try to manipulate massive data sets in excel - which I think is a good thing. It's much easier to check some code than some of the complex spreadsheets I've seen created in my organisation. A good example is manipulation of harmonic impedance data for contingency analysis in power systems - this took an engineer 2 weeks in excel - 3000 lines of Fortran does the same job in 20 minutes - including generating all the required plots.

Thanks again

Ken
Back to top
View user's profile Send private message Visit poster's website
John-Silver



Joined: 30 Jul 2013
Posts: 1520
Location: Aerospace Valley

PostPosted: Mon Mar 20, 2017 11:44 pm    Post subject: Reply with quote

I note from the ddl5 ReadMe that there's no mention of the logarithmic scales update in this beta release, I assume that is still to come shortly as foreseen last week or is it just not dovumented in the readme ? ?
Back to top
View user's profile Send private message
DanRRight



Joined: 10 Mar 2008
Posts: 2813
Location: South Pole, Antarctica

PostPosted: Mon Mar 20, 2017 11:56 pm    Post subject: Reply with quote

Ken, We all learn from each other here. I have question to you too - what settings in native %pl did you use in the last plots to get x and y axis linewidths more then 1 pixel wide? It clearly is not "etched"
Back to top
View user's profile Send private message
John-Silver



Joined: 30 Jul 2013
Posts: 1520
Location: Aerospace Valley

PostPosted: Tue Mar 21, 2017 12:19 am    Post subject: Reply with quote

I know my eyesight's bad but I don't see any difference in thickness of the axes compared with earkėlier plots at beginning of this post !

Quote:
%pl[etched] ....... thicken the axes and tick marks.

doesn't seem to allow user to specify a particular thickness, so presumeably it's just 1 pixel (default) or ... ? 2 ?
Back to top
View user's profile Send private message
Kenneth_Smith



Joined: 18 May 2012
Posts: 697
Location: Hamilton, Lanarkshire, Scotland.

PostPosted: Tue Mar 21, 2017 12:20 am    Post subject: Reply with quote

Dan, John,

The plots in the previous post did not use the new options in the latest dll from Paul (no 5)

Using these options with the new dll:-

Code:
      call winop@("%pl[smoothing=4]")
      call winop@("%pl[framed]")
      call winop@("%pl[margin=30]")
      call winop@("%pl[etched]")


Produced the following:-




The abscissa and ordinate are slightly thicker. The etched option does not accept a numerical value, so cannot make the lines thicker than this example.
Back to top
View user's profile Send private message Visit poster's website
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 7916
Location: Salford, UK

PostPosted: Tue Mar 21, 2017 8:14 am    Post subject: Reply with quote

John

Logarithmic scales are implemented in the latest DLLs.

Kenneth

Can you check the effect of using [link=lines] against [link=curves]. They were implemented the wrong way round in some contexts. You need "lines" to avoid overshoot with step like functions.
Back to top
View user's profile Send private message AIM Address
Kenneth_Smith



Joined: 18 May 2012
Posts: 697
Location: Hamilton, Lanarkshire, Scotland.

PostPosted: Tue Mar 21, 2017 9:57 am    Post subject: Reply with quote

Apologies Paul, [link=lines] and [link=curves] is fine as this example shows:-

Code:
      program test
      implicit none
      include<windows.ins>
      real(kind=2) x(1:500), y(1:500), t, dt, tstart
      integer i
      tstart = 1.d0 ; t  = 0.d0 ;  dt = 0.01d0 ; x  = 0.d0 ; y  = 0.d0
      do i = 1, 500, 1
        x(i) = t
        if (t .ge. tstart) y(i) = 1.d0
        t = t + dt
        write(6,*) x(i), y(i)
      end do
     
      i = winio@('%ww&')
      call winop@("%pl[native]")
      call winop@("%pl[x_array]")
      call winop@("%pl[smoothing=4]")
      call winop@("%pl[framed]")
      call winop@("%pl[colour=blue]")
      call winop@("%pl[width=2]")
      call winop@("%pl[margin=30]")
      call winop@("%pl[etched]")
      call winop@("%pl[link=lines]")
      call winop@("%pl[title=Lines]")
      i = winio@('%pl&',300,250,500,x,y)

      call winop@("%pl[native]")
      call winop@("%pl[x_array]")
      call winop@("%pl[smoothing=4]")
      call winop@("%pl[framed]")
      call winop@("%pl[colour=blue]")
      call winop@("%pl[width=2]")
      call winop@("%pl[margin=30]")
      call winop@("%pl[etched]")
      call winop@("%pl[link=curves]")
      call winop@("%pl[title=Curves]")
      i = winio@('%pl',300,250,500,x,y)
     
      end test


Which produces



There's something else that's causing a problem in my longer/more complex code which I'll need to track down. Can you please confirm the format of the numerical values for x_min, y_max etc, i.e. what is correct:-
Code:
call winop@("%pl[y_max=1.2d0]")

or
Code:
call winop@("%pl[y_max=1.2]")


Thanks Ken
Back to top
View user's profile Send private message Visit poster's website
DanRRight



Joined: 10 Mar 2008
Posts: 2813
Location: South Pole, Antarctica

PostPosted: Tue Mar 21, 2017 10:22 am    Post subject: Reply with quote

Ken, John,
Then obviously the Ken's graphs look here better then they actually are. Because either posting service, or the browser, or the lose graphics JPG format was used, which scale the lines from their original 1 pixel size, or better say distort, doing that by antialiasing way. To see that i made PrintScreen and magnified plots above and my own plots. I used lossless PNG format. Compare axis Ken plotted at the left with my plot at the right below. In my plot axis width is not broadened by fake antialiasing, it is strictly 1 pixel.

By the way noticed the way Silverfrost realized "etching" ? Left and bottom axis have approximately 1.5 pixel linewidth. If it is done by antialiasing (Clearwin is specifically good at that, better then most professional software, see the curves when smoother) then the linewidth could be not integer number 1,2,3 ... which is very crude but floating point number like 1.5, 2.3, 3.4 ... Would be very good if Silverfrost implemented axis linewidth parameter and have done that the way like the etching was done.



Last edited by DanRRight on Tue Mar 21, 2017 8:20 pm; edited 10 times in total
Back to top
View user's profile Send private message
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 7916
Location: Salford, UK

PostPosted: Tue Mar 21, 2017 10:23 am    Post subject: Reply with quote

You should use 1.2, 1.2e0 or 1.2E0. In C, sscanf is called using %f.
Back to top
View user's profile Send private message AIM Address
Kenneth_Smith



Joined: 18 May 2012
Posts: 697
Location: Hamilton, Lanarkshire, Scotland.

PostPosted: Tue Mar 21, 2017 10:13 pm    Post subject: Reply with quote

Thanks Paul.

The code below replicates the problem I've observed in my much larger program. Originally I thought there was some dependency on the order in which the %pl options are assembled into the %pl string. In both cases below the %pl options are the same, only the order of the options is different. In both cases [link=lines].

Code:
      program test
      implicit none
      include<windows.ins>
      real(kind=2) x(1:500), y(1:500), t, dt, tstart
      integer plot1, plot2, plot3, plot4
      integer i
      tstart = 1.d0 ; t  = 0.d0 ;  dt = 0.01d0 ; x  = 0.d0 ; y  = 0.d0
      do i = 1, 500, 1
        x(i) = t
        if (t .ge. tstart) y(i) = 1.d0
        t = t + dt
        write(6,*) x(i), y(i)
      end do
     
      i = winio@('%ww&')
      call winop@("%pl[native]")
      call winop@("%pl[x_array]")
      call winop@("%pl[framed]")
      call winop@("%pl[colour=blue]")
      call winop@("%pl[width=2]")
      call winop@("%pl[link=lines]")
      i = winio@('%`pl&',300,250,500,x,y, plot2)

      call winop@("%pl[native]")
      call winop@("%pl[colour=blue]")
      call winop@("%pl[width=2]")
      call winop@("%pl[framed][link=lines]") !### comment out this line
!     call winop@("%pl[link=lines]")         !    and replace with this line
      call winop@("%pl[x_array]")
      i = winio@('%`pl',300,250,500,x,y, plot3)
      end test


which produces this plot, link=lines is not effective in the second plot



I then found that if you comment out
Code:
call winop@("%pl[framed][link=lines]")
in the second %pl sequence, and replace it with
Code:
call winop@("%pl[link=lines]")
, i.e. remove the reference to [framed], the second plot is correctly generated as shown below (but obviously there is now no frame).




So the problem seems to be related to the combination of [link=lines] and [framed].

Apologies for continuing to pester you with this.

Regards Ken
Back to top
View user's profile Send private message Visit poster's website
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 7916
Location: Salford, UK

PostPosted: Wed Mar 22, 2017 7:48 am    Post subject: Reply with quote

The syntax %pl[framed][link=lines] is incorrect it should be %pl[framed,link=lines].

ClearWin+ should have faulted this.
Back to top
View user's profile Send private message AIM Address
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> ClearWin+ All times are GMT + 1 Hour
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Page 4 of 8

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group