Ciao Niccolò, ovviamente dovrai utilizzare un timestep adeguato alla precipitazione, nel senso che se hai eventi molto brevi conviene avere un timestep breve, altrimenti si può anche allungare. Il problema che riscontri tu io non lo ho mai visto, potresti mandarci il file della precipitazione in modo da capire se stai inserendo tutti i dati in modo corretto?
Grazie, Silvia On Mon, Sep 17, 2018 at 2:49 PM Niccolo Tubini <tubini.nicc...@gmail.com> wrote: > Ciao a tutti, > > ho lanciato una simulazione con una precipitazione registrata, intervallo > di campionamento 5 minuti. > Il time step dell'idrogramma calcolato varia tra 1 e 2 minuti. Per > correggerlo devo considerare un time step di 5 minuti, pari a quello della > precipitazione, o un time step di 1 minuto? > Se considero un time step di 5 minuti il picco di piena e` circa 11 ore > dopo l'inizio della precipitazione, per un bacino di 1km2 mi sembra tanto. > Con un time step di 1 minuto il picco e` prima dell'inizio della > precipitazione. > > Grazie in anticipo, > Niccolo` > > Il giorno mar 28 ago 2018 alle ore 11:36 Niccolo Tubini < > tubini.nicc...@gmail.com> ha scritto: > >> ok, e il timestep e` 1 minuto giusto? >> >> >> >> Il giorno mar 28 ago 2018 alle ore 11:35 Silvia Franceschi < >> silvia.frances...@gmail.com> ha scritto: >> >>> Ciao Niccolò, >>> credo che la differenza sia dovuta a due modi diversi di calcolare la >>> portata massima, ovvero nel log vedi il calcolo diretto nell'istante esatto >>> del massimo, mentre nel CSV il calcolo è fatto rispettando gli intervalli >>> di tempo indicati. E' anche normale che ci siano intervalli un po' diversi, >>> in realtà sarebbero arrotondati... ma lo puoi fare a mano. >>> >>> Silvia >>> >>> >>> On Tue, Aug 28, 2018 at 9:50 AM Niccolo Tubini <tubini.nicc...@gmail.com> >>> wrote: >>> >>>> Ciao Silvia, >>>> >>>> la celerita` 4m/s l'ho messa per vedere cosa sarebbe cambiato a parita` >>>> degli altri input rispetto all'idrogramma ottenuto con una celerita` di >>>> 2m/s. Mi rendo conto che e` alta pero` essendo la prima volta che usavo >>>> peakflow volevo capire come i vari input incidessero sul risultato della >>>> simulazione. >>>> Il bacino su cui sto lavorando e` il Rio secco (area ~1.4 Km2 e >>>> lunghezza dell'asta principale ~2km). >>>> >>>> Ho rilanciato la simulazione e ottengo gli stessi valori. Abbasando il >>>> valore della celerita` a 3m/s nel log leggo 38.79 m3/s e nel csv 35.05, con >>>> 2m/s nel log 26.72 m3/s e nel csv 26.95 m3/s. >>>> >>>> Un'altra cosa (spero l'ultima) il timestep dell'idrogramma non e` >>>> costante >>>> 2018-08-28 06:44,0.0 >>>> ,2018-08-28 06:46,3.3871822587362477 >>>> ,2018-08-28 06:48,11.024139734276767 >>>> ,2018-08-28 06:49,17.5583421869693 >>>> ,2018-08-28 06:51,23.00152613016996 >>>> ,2018-08-28 06:53,26.954433356925595 >>>> ,2018-08-28 06:54,23.025622427416245 >>>> a volte e` 1 minuto altre volte 2, e` normale? >>>> >>>> Grazie ancora della disponibilita`, ciao >>>> Niccolo` >>>> >>>> Il giorno lun 27 ago 2018 alle ore 20:50 Silvia Franceschi < >>>> silvia.frances...@gmail.com> ha scritto: >>>> >>>>> Ciao Niccolò, >>>>> la durata della precipitazione è in minuti, riguardo invece la portata >>>>> massima, di solito differenzia di un pochino tra log e file però in questo >>>>> caso mi pare esagerata la differenza. Sei sicuro di star guardando il CSV >>>>> corretto? inoltre la velocità di 4 m/s che hai impostato mi sembra un >>>>> pochino alta, che bacino hai? >>>>> >>>>> Silvia >>>>> >>>>> >>>>> On Fri, Aug 24, 2018 at 1:45 PM Niccolo Tubini < >>>>> tubini.nicc...@gmail.com> wrote: >>>>> >>>>>> Ciao a tutti, >>>>>> >>>>>> ho lanciato il comando Peakflow e nella finestra Spatial Toolbox log >>>>>> leggo questo >>>>>> Process started: 2018-08-24 12:35:43 >>>>>> ------------------------------>8---------------------------- >>>>>> Launching command: >>>>>> ------------------ >>>>>> C:\Program >>>>>> Files\gvSIG-desktop\gvSIG-desktop-2.4.0\gvSIG\extensiones\jre\bin\java.exe >>>>>> -Xmx2000m -cp >>>>>> "C:\Users\Niccolo\gvSIG\installation\gvSIG\extensiones\org.hortonmachine.gvsig.base\lib\groovy-all-2.4.6.jar;C:\Users\Niccolo\gvSIG\installation\gvSIG\extensiones\org.hortonmachine.gvsig.base\lib/*;." >>>>>> groovy.ui.GroovyMain >>>>>> C:\Users\Niccolo\AppData\Local\Temp\hm_script_330421177113872359.groovy >>>>>> (you can run the above from command line, customizing the content) >>>>>> ----------------------------------->8--------------------------------- >>>>>> >>>>>> Script run: >>>>>> ----------- >>>>>> org.hortonmachine.modules.Peakflow _peakflow = new >>>>>> org.hortonmachine.modules.Peakflow(); >>>>>> _peakflow.pA = 49.5; >>>>>> _peakflow.pSat = 80; >>>>>> _peakflow.pCelerity = 4; >>>>>> _peakflow.outDischarge = """C:/Users/Niccolo/Documents/provaQ.csv"""; >>>>>> _peakflow.inTopindex = >>>>>> """C:/Users/Niccolo/gvSIG-workspace/RioSecco_5m_25832/top_index_corrected_cut.asc"""; >>>>>> _peakflow.inRescaledsub = >>>>>> """C:/Users/Niccolo/gvSIG-workspace/RioSecco_5m_25832/resc_dist_r100_80_sub_cut.asc"""; >>>>>> _peakflow.inRescaledsup = >>>>>> """C:/Users/Niccolo/gvSIG-workspace/RioSecco_5m_25832/resc_dist_r5_80_sup_cut.asc"""; >>>>>> _peakflow.pN = 0.32; >>>>>> _peakflow.pDiffusion = 1000; >>>>>> _peakflow.process(); >>>>>> println "" >>>>>> println "" >>>>>> >>>>>> ------------------------------>8---------------------------- >>>>>> Reading coverage: top_index_corrected_cut.asc >>>>>> Finished. >>>>>> Reading coverage: resc_dist_r5_80_sup_cut.asc >>>>>> Finished. >>>>>> Reading coverage: resc_dist_r100_80_sub_cut.asc >>>>>> Finished. >>>>>> Vectorizing double vectors >>>>>> Sorting... >>>>>> ... >>>>>> Finished. >>>>>> Splitting real vectors >>>>>> 1 empty bins where found >>>>>> Creating new matrix >>>>>> Vectorizing double vectors >>>>>> Sorting... >>>>>> ... >>>>>> Finished. >>>>>> Splitting real vectors >>>>>> Creating new matrix >>>>>> Vectorizing double vectors >>>>>> Sorting... >>>>>> ... >>>>>> Finished. >>>>>> Splitting real vectors >>>>>> 12 empty bins where found >>>>>> Creating new matrix >>>>>> Peakflow launched in statistic mode... >>>>>> IUH Diffusion... >>>>>> Calculating diffusion... >>>>>> 0%... >>>>>> 10%... >>>>>> 20%... >>>>>> 30%... >>>>>> 40%... >>>>>> 50%... >>>>>> 60%... >>>>>> 70%... >>>>>> 80%... >>>>>> 90%... >>>>>> 100%... >>>>>> Finished. >>>>>> Calculating subsurface IUH... >>>>>> 10%... >>>>>> 20%... >>>>>> 30%... >>>>>> 40%... >>>>>> 50%... >>>>>> 60%... >>>>>> 70%... >>>>>> 80%... >>>>>> 90%... >>>>>> 100%... >>>>>> Finished. >>>>>> IUH Diffusion... >>>>>> 0%... >>>>>> 10%... >>>>>> 20%... >>>>>> 30%... >>>>>> 40%... >>>>>> 50%... >>>>>> 60%... >>>>>> 70%... >>>>>> 80%... >>>>>> 90%... >>>>>> 100%... >>>>>> Finished. >>>>>> Statistic Jeff... >>>>>> Q calculation... >>>>>> Calculating Jeff... >>>>>> Calculating discharge for t < tcorr... >>>>>> 0%... >>>>>> 10%... >>>>>> 20%... >>>>>> 30%... >>>>>> 40%... >>>>>> 50%... >>>>>> 60%... >>>>>> 70%... >>>>>> 80%... >>>>>> 90%... >>>>>> 100%... >>>>>> Finished. >>>>>> Calculating discharge for t > tcorr... >>>>>> 0%... >>>>>> 10%... >>>>>> 20%... >>>>>> 30%... >>>>>> 40%... >>>>>> 50%... >>>>>> 60%... >>>>>> 70%... >>>>>> 80%... >>>>>> 90%... >>>>>> 100%... >>>>>> Finished. >>>>>> Maximum rainfall duration: 115.0 >>>>>> Maximum discharge value: 50.25414096383695 >>>>>> >>>>>> >>>>>> Process finished: 2018-08-24 12:35:52 >>>>>> >>>>>> Quando pero` apro il file .csv di output la portata massima e` pari a >>>>>> 37.76900478990363, la portata massima corretta e` quella nel .csv? >>>>>> Riporto le prime righe del .csv >>>>>> @H,date,discharge >>>>>> Format,yyyy-MM-dd HH:mm, >>>>>> Type,Date, >>>>>> ,2018-08-24 10:35,0.0 >>>>>> ,2018-08-24 10:37,37.76900478990363 >>>>>> ,2018-08-24 10:39,35.33001832680685 >>>>>> ,2018-08-24 10:40,20.212508980665184 >>>>>> ,2018-08-24 10:42,13.446104538944528 >>>>>> ,2018-08-24 10:44,9.892880269987524 >>>>>> ,2018-08-24 10:45,7.5939577680423245 >>>>>> ,2018-08-24 10:47,6.011784274922036 >>>>>> ,2018-08-24 10:49,4.929564446763167 >>>>>> ,2018-08-24 10:50,4.122217965006686 >>>>>> ,2018-08-24 10:52,3.531891748182115 >>>>>> >>>>>> Inoltre volevo chiedere se la durata della precipitazione riportata >>>>>> nel log e` espressa in minuti. >>>>>> >>>>>> Grazie in anticipo, >>>>>> Niccolo` >>>>>> _______________________________________________ >>>>>> gvSIG-Italian mailing list >>>>>> gvSIG-Italian@lists.osgeo.org >>>>>> https://lists.osgeo.org/mailman/listinfo/gvsig-italian >>>>>> >>>>> >>>>> >>>>> -- >>>>> ing. Silvia Franceschi >>>>> Via Latemar, 22 >>>>> 38030 Castello di Fiemme (TN) >>>>> >>>>> tel: 0039 -3384501332 >>>>> _______________________________________________ >>>>> gvSIG-Italian mailing list >>>>> gvSIG-Italian@lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/gvsig-italian >>>>> >>>> _______________________________________________ >>>> gvSIG-Italian mailing list >>>> gvSIG-Italian@lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/gvsig-italian >>>> >>> >>> >>> -- >>> ing. Silvia Franceschi >>> Via Latemar, 22 >>> 38030 Castello di Fiemme (TN) >>> >>> tel: 0039 -3384501332 >>> _______________________________________________ >>> gvSIG-Italian mailing list >>> gvSIG-Italian@lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/gvsig-italian >>> >> _______________________________________________ > gvSIG-Italian mailing list > gvSIG-Italian@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/gvsig-italian > -- ing. Silvia Franceschi Via Latemar, 22 38030 Castello di Fiemme (TN) tel: 0039 -3384501332
_______________________________________________ gvSIG-Italian mailing list gvSIG-Italian@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gvsig-italian
